On Sun, Jan 14, 2018 at 2:38 AM, Chapman Flack
wrote:
> On 01/13/18 21:36, Everaldo Canuto wrote:
>
> > I don't wanna be irritating but here every postgres user I found really
> > can't understand how the original patch was not accepted, people against
> it
> &
On Sat, Jan 13, 2018 at 11:31 PM, Tom Lane wrote:
> Vik Fearing writes:
> > After re-reading the thread, I think the original patch is optimal.
>
> Hm, few other people thought that.
>
>
I don't wanna be irritating but here every postgres user I found really
can't understand how the original pat
Change my patch will make psql different from other sql clients I use
(sqlplus and mysql).
I am happy with my custom version of psql so you can cancel/delete/ignore
my patch.
On Sun, Jan 7, 2018 at 12:36 AM, Tom Lane wrote:
> Everaldo Canuto writes:
> > Can we proceed with current
On Tue, Dec 12, 2017 at 2:39 PM, Everaldo Canuto
wrote:
>
> As others have pointed out, there are _far_ more frustrating things
>> (like the lack of SHOW CREATE [TABLE|etc]... support in the backend)
>> for anyone coming from mysql that I would suggest should be addressed
>
On Tue, Dec 12, 2017 at 1:02 PM, Geoff Winkless wrote:
>
> There is also stackexchange question with 51000 views that asks how to
> start the postgresql client. Should we rename psql to mysql to help
> new users too?
>
No, we shouldn't but it will help a lot is postgres client have names like
"po
Hello.
On Mon, Dec 11, 2017 at 11:14 AM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
> And what about create some way to create aliases for meta-commands in
> psql? Something like:
>
> \alias quit \q
> \alias exit \q
>
> We also can create a special config variable to enable/disab
On Sat, Dec 9, 2017 at 11:36 AM, Daniel Vérité"
wrote:
>
> postgres=> select 2+2
>2-> help
>3-> quit
>4-> exit
I like it! Maybe another proposal to change PROMPT2?
On Fri, Dec 8, 2017 at 2:26 PM, Vladimir Svedov wrote:
> I wonder if *exit;* to terminate loop be confused with exit psql in case
> of bad syntax. then instead of reporting error in plpgsql it would just
> silently exit?..
>
I just tested it and works as expected. Second line of patch takes care
Hello,
On Fri, Dec 8, 2017 at 11:57 AM, Daniel Vérité"
wrote:
> Implementing it is easy, but it might be a hard sell for the project
> because it creates a precedent.
>
We already have "help" (without slash) so I don't think it is a precedent.
> The next question in that list is "PostgreSQL
On Fri, Dec 8, 2017 at 8:10 AM, Michael Paquier
wrote:
>
> I think that you are going to need better reasons than just being more
> friendly with other database clients by breaking a rule which is
> around for 20 years.
Well, that reason was enough for other sql clients to implement "\q" and
"\q
On Fri, Dec 8, 2017 at 4:00 AM, Laurenz Albe
wrote:
> I am -1 on that, because I think that it is not good to break the simple
> rule
> that everything that is a psql command starts with a backslash.
>
We already have "help" command without slash and that is why I implement in
the same way help
On Fri, Dec 8, 2017 at 5:22 AM, Sergei Kornilov wrote:
> Why not just use ctrl+D shortcut? This EOF signal works both in bash,
> mysql, psql, any CLI tool which I remember
>
Because like I wrote, other sql clients also support "exit" and "quit".
hat I am
the only that sometimes try to exit psql with "exit'.
The attached patch implements this way to exit psql.
Regards
--
Everaldo Canuto
psql-exit-quit.patch
Description: Binary data
13 matches
Mail list logo
