From: | John McKown <john(dot)archie(dot)mckown(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Allow disabling folding of unquoted identifiers to lowercase |
Date: | 2016-04-29 20:44:15 |
Message-ID: | CAAJSdjjW=1bZoifUpD1kY0i8AO6AskMa88UizyZnmNUmGm+PwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Apr 29, 2016 at 3:38 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 4/29/2016 12:56 PM, John McKown wrote:
>
> 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.
>
>
> are those the APIs the parser uses?
>
​Ah. Good point. I ASSuMEd that what any C language program would use.
IIRC, PostgreSQL uses Bison and Flex to generate the parsing grammars, and
I don't know what those products output.​
>
>
> --
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | John McKown | 2016-04-29 21:13:33 | Re: Allow disabling folding of unquoted identifiers to lowercase |
Previous Message | John R Pierce | 2016-04-29 20:38:22 | Re: Allow disabling folding of unquoted identifiers to lowercase |