Re: Discussion: psql \et -> edit the trigger function
От | Kirk Wolak |
---|---|
Тема | Re: Discussion: psql \et |
Дата | |
Msg-id | CACLU5mQ1q_qDd3wtvFtOVvjySjL5Xin+u_Zawz75RW=D_NVt-A@mail.gmail.com обсуждение исходный текст |
Ответ на |
Re: Discussion: psql \et |
Ответы |
Re: Discussion: psql \et Re: Discussion: psql \et |
Список | pgsql-hackers |
On Wed, May 10, 2023 at 12:20 PM Pavel Stehule <pavel.stehule@gmail.com> wrote:
Hist 10. 5. 2023 v 17:33 odesílatel Kirk Wolak <wolakk@gmail.com> napsal:We already have\ef\evThe use case here is simply that it saves me from:\d <table>[scroll through all the fields][often scroll right]select function name\ef [paste function name]and tab completion is much narrowerWhen doing conversions and reviews all of this stuff has to be reviewed.Oftentimes, renamed, touched.I am 100% willing to write the code, docs, etc. but would appreciate feedback.\et can be little bit confusing, because looks like editing trigger, not trigger functionwhat \eft triggername?
Pavel, I am "torn" because of my OCD, I would expect
\eft <TAB>
to list functions that RETURN TRIGGER as opposed to the level of indirection I was aiming for.
where
\et <TAB>
Would specifically let me complete the Trigger_Name, but find the function
It makes me wonder, now if:
\etf
Is better for this (edit trigger function... given the trigger name).
And as another poster suggested. As we do the AUTOCOMPLETE for that, we could address it for:
\ef?
because:
\eft <TAB>
is valuable as well, and deserves to work just like all \ef? items
It seems like a logical way to break it down.
regardsPavelKirk...
В списке pgsql-hackers по дате отправления: