From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | stefan(at)extum(dot)com, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-sql(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: [SQL] id and ID in CREATE TABLE |
Date: | 2002-07-19 17:33:29 |
Message-ID: | 13931.1027100009@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
> Agreed. Absolutely. But, since the SQL standard says upper case,
> wouldn't it be useful to at least have a switch (run time, initdb time,
> or ./configure time???) called something like FOLDTOUPPER (in upper case
> of course :-)
The main problem with this is what do you do with the system catalogs?
If we start folding to upper case then existing clients will break
unless we also rename pg_class to PG_CLASS, etc; and that will break
them anyway if they wrote "pg_class".
I don't believe that conforming to this particular small aspect of the
spec is worth the pain it would cause.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tim | 2002-07-19 18:10:30 | RAD web development with PostgreSQL? |
Previous Message | Bruce Momjian | 2002-07-19 17:32:57 | Re: [GENERAL] Some Solaris notes, and an invitation |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-19 17:53:45 | Re: Two Index Questions |
Previous Message | Bruce Momjian | 2002-07-19 17:29:16 | Re: [SQL] id and ID in CREATE TABLE |