Re: Review: query result history in psql
| От | Maciej Gajewski |
|---|---|
| Тема | Re: Review: query result history in psql |
| Дата | |
| Msg-id | CAEcSYXLXM7bUqyxKMwdf5wciZGiNmc_HZ1TLT-mST3KKvRGnHQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Review: query result history in psql (ian link <ian@ilink.io>) |
| Ответы |
Re: Review: query result history in psql
|
| Список | pgsql-hackers |
I'm not really bought into some of the ideas.
but maybe some interactive mode should be usefull - so after
execution, and showing result, will be prompt if result should be
saved or not.I like the idea, in addition to the ordinary mode. Personally, I would use the ordinary mode, but I can see how 'interactive' would be useful.
This would require a complex change to the client code. And the result would eventually become annoying: an interactive question after each and every query. Currently, when turned on, every result is stored and simple notification is printed.
yes, the names :ans01, :ans02, ... miss semantics - How I can jointhis name (and content) with some SQL query?That makes sense. I think having part of / the whole query string would be very helpful. Great suggestion!
The naming is obscure and non-informative, I agree. If you have a nice idea how to make it better, I'd love to discuss it. But please remember that it has one huge advantage: simplicity. The client is a classical command-line tool, and as such it delegates some of the functionality to external programs, like pager or terminal.
I'm pretty sure that your terminal emulator has a 'find' function that would allow you to quickly locate the variable and associated query in the scrollback.
M
В списке pgsql-hackers по дате отправления: