RE: Support tab completion for upper character inputs in psql - Mailing list pgsql-hackers

From Tang, Haiying
Subject RE: Support tab completion for upper character inputs in psql
Date
Msg-id 696766648c7a4266864f843b0e4140dd@G08CNEXMBPEKD05.g08.fujitsu.local
Whole thread Raw
In response to Re: Support tab completion for upper character inputs in psql  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses RE: Support tab completion for upper character inputs in psql
List pgsql-hackers
At Sun, 07 Feb 2021 13:55:00 -0500, Tom Lane <tgl@sss.pgh.pa.us> wrote in
>
> This looks like you're trying to force case-insensitive behavior
> whether that is appropriate or not.  Does not sound like a good idea.

Thanks for your reply.
I raise this issue because I thought all SQL command should be case-insensitive.
And the set/reset/show commands work well no matter the input configuration parameter is in upper or in lower case.
My modification is not good enough, but I really think it's more convenient if we can support the tab-completion for
uppercharacter inputs. 

=# set APPLICATION_NAME to test;
SET

=# show APPLICATION_name;
 application_name
------------------
 test
(1 row)

From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Sent: Monday, February 8, 2021 5:02 PM

>However set doesn't. If it is what is wanted, the following change on Query_for_list_of_set_vars works (only for the
caseof SET/RESET commands). 

Thanks for your update. I applied your patch, it works well for SET/RESET commands.
I added the same modification to SHOW command. The new patch(V2) can support tab completion for upper character inputs
inpsql for SET/RESET/SHOW commands. 

Regards,
Tang



Attachment

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Is Recovery actually paused?
Next
From: John Naylor
Date:
Subject: Re: [POC] verifying UTF-8 using SIMD instructions