From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, gearond(at)cvc(dot)net, Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: The folding of unquoted names to lower case in PostgreSQL |
Date: | 2003-03-14 22:01:22 |
Message-ID: | 23935.1047679282@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
> Now that catalogs live in the
> pg_catalog schema, I could just treat anything in the pg_catalog to be
> fold to lower, while everything else would fold to upper.
And you will determine whether something is in pg_catalog how, when you
haven't yet done a catalog lookup for it?
Keep in mind that the problem exists not only for system catalog names,
but for column names in those catalogs, not to mention built-in
functions. So looking at whether the name starts with "pg_" really
doesn't get you far as a way of deciding which way to fold.
Possibly you could make something of "fold to upper case originally,
but refold to lower case before looking in pg_catalog". I have no idea
how to implement that in a way that's not a horrid kluge though. Also,
it'd likely have unpleasant failure modes in some non-ASCII locales
where upcasing and downcasing aren't quite inverses. (Check the
archives for past problems with keywords in Turkish...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dennis Gearon | 2003-03-14 22:11:59 | Re: The folding of unquoted names to lower case in PostgreSQL |
Previous Message | P G | 2003-03-14 21:45:04 | Re: [GENERAL] Is there any procedure to start postgre database server automatically |