Re: Support tab completion for upper character inputs in psql
| От | Tom Lane |
|---|---|
| Тема | Re: Support tab completion for upper character inputs in psql |
| Дата | |
| Msg-id | 964540.1643753218@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Support tab completion for upper character inputs in psql (Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>) |
| Список | pgsql-hackers |
=?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= <ilmari@ilmari.org> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>>> We could do something hacky like matching case only when there's
>>> no longer any matching object names, but that might be too magic.
>> I experimented with that, and it actually doesn't seem as weird
>> as I feared. See if you like this ...
> That's a reasonable compromise, and the implementation is indeed less
> hacky than one might have feared. Although I think putting the
> `num_keywords` variable before `num_other` would read better.
Hm... I renamed "num_other" to "num_query_other" instead.
> Going through the uses of COMPLETE_WITH(_SCHEMA)_QUERY_PLUS, I noticed a
> few that had the keywords in lower case, which is fixed in the attached
> patch (except the hardcoded data types, which aren't really keywords).
Yeah, my oversight. Pushed.
regards, tom lane
В списке pgsql-hackers по дате отправления: