Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id A35AE47598F for ; Fri, 19 Jul 2002 13:34:42 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g6JHXTVk013932; Fri, 19 Jul 2002 13:33:29 -0400 (EDT) To: "scott.marlowe" Cc: stefan@extum.com, Martijn van Oosterhout , pgsql-sql@postgresql.org, pgsql-general@postgresql.org Subject: Re: [SQL] id and ID in CREATE TABLE In-reply-to: References: Comments: In-reply-to "scott.marlowe" message dated "Fri, 19 Jul 2002 10:53:50 -0600" Date: Fri, 19 Jul 2002 13:33:29 -0400 Message-ID: <13931.1027100009@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200207/1233 X-Sequence-Number: 27720 "scott.marlowe" 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