From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Lee Hachadoorian <Lee(dot)Hachadoorian+L(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: SQL keywords are suddenly case sensitive |
Date: | 2013-04-16 23:31:44 |
Message-ID: | 516DDF60.5010401@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/16/2013 02:46 PM, Lee Hachadoorian wrote:
> List,
>
> SQL seems to be behaving in a case-sensitive manner:
>
> universe=# select 1;
> ?column?
> ----------
> 1
> (1 row)
>
> universe=# SELECT 1;
> ERROR: syntax error at or near "SELECT 1"
> LINE 1: SELECT 1;
> ^
> I cannot figure out how this happened, and Google is not helping because
> all I'm getting is information about case-sensitivity in identifiers or
> in string comparison. I didn't even think this was possible, as I've
> always switched between lower case and upper case keywords, usually
> using lower case while testing and upper case to prettify scripts that I
> will be saving for reuse.
Interesting.
Does this behavior survive logging out and then back into a session?
Do you have any other client using the database that exhibits this behavior?
> Regards,
> --Lee
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-04-16 23:34:25 | Re: SQL keywords are suddenly case sensitive |
Previous Message | Adrian Klaver | 2013-04-16 23:29:10 | Re: Can you spot the difference? |