Re: Allow disabling folding of unquoted identifiers to lowercase

Поиск
Список
Период
Сортировка
От John McKown
Тема Re: Allow disabling folding of unquoted identifiers to lowercase
Дата
Msg-id CAAJSdjhbcZfA1Qt9OZB+X_jVEGL5SgYvT=kH0KQRuSweiYNANg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Allow disabling folding of unquoted identifiers to lowercase  (John R Pierce <pierce@hogranch.com>)
Ответы Re: Allow disabling folding of unquoted identifiers to lowercase  (John R Pierce <pierce@hogranch.com>)
Список pgsql-general
Дерево обсуждения
On Fri, Apr 29, 2016 at 2:44 PM, John R Pierce <pierce@hogranch.com> wrote:
On 4/29/2016 10:21 AM, Evgeny Morozov wrote:
It would be great if Postgres had a server setting that allowed the automatic folding of identifiers to lowercase to be disabled, so that camel case identifiers could be used without having to quote every single identifier, i.e.

SELECT MyColumn FROM MyTable ORDER BY MyColumn

instead of

SELECT "MyColumn" FROM "MyTable" ORDER BY "MyColumn"

I suspect this would be painful for the parser, unless you also enforced that all SQL keywords were in a specific case (all lower would be the minimal impact to the code).   otherwise the parser would have to lower() every token to check to see if its a keyword, but if not, revert it to its original case.


​Why? PostgreSQL is written in C. So use strncasecmp() instead of strncmp() or strcasecmp() instead of strcmp() to test for a token.
-- 
john r pierce, recycling bits in santa cruz



--
The unfacts, did we have them, are too imprecisely few to warrant our certitude.

Maranatha! <><
John McKown

В списке pgsql-general по дате отправления:

Предыдущее
От: Ciprian Grigoras
Дата:
Сообщение: Re: Postgres processes getting stuck (bug?)
Следующее
От: John R Pierce
Дата:
Сообщение: Re: Allow disabling folding of unquoted identifiers to lowercase