| From: | Victor Spirin <v(dot)spirin(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: psql tab-complete |
| Date: | 2019-10-24 21:53:02 |
| Message-ID: | 9dec5038-548e-91f9-df14-8825f7aa7c5c@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Yes, I found, that VA_ARGS_NARGS(__ VA_ARGS__) macros always return 1 on
Windows.
Victor Spirin
Postgres Professional:http://www.postgrespro.com
The Russian Postgres Company
25.10.2019 0:48, Tom Lane пишет:
> Victor Spirin <v(dot)spirin(at)postgrespro(dot)ru> writes:
>> I found some problem with tab-complete in the 12 version. I checked
>> this in the Windows.
> This change seems to break the case intended by the comment,
> ie given the context
>
> SELECT * FROM tablename WHERE <tab>
>
> we want to offer the columns of "tablename" as completions.
>
> I'd be the first to agree that that's completely lame, as there
> are any number of related cases it fails to cover ... but this
> patch isn't making it better.
>
> regards, tom lane
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Soumyadeep Chakraborty | 2019-10-24 21:59:21 | Re: WIP: expression evaluation improvements |
| Previous Message | Tom Lane | 2019-10-24 21:48:31 | Re: psql tab-complete |