From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200207191729.g6JHTGD29488@candle.pha.pa.us>
Subject: Re: [SQL] id and ID in CREATE TABLE
In-Reply-To: <Pine.LNX.4.44.0207191051550.3990-100000@css120.ihs.com>
To: "scott.marlowe" <scott.marlowe@ihs.com>
Date: Fri, 19 Jul 2002 13:29:16 -0400 (EDT)
Cc: Tom Lane <tgl@sss.pgh.pa.us>, stefan@extum.com,
	Martijn van Oosterhout <kleptog@svana.org>, pgsql-sql@postgresql.org,
	pgsql-general@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

scott.marlowe wrote:
> On Fri, 19 Jul 2002, Tom Lane wrote:
> 
> > stefan@extum.com writes:
> > > But anyway this is not so important, but why upper cases are bad ?
> > 
> > It's well established that all-lower-case text is more readable than
> > all-upper-case ... 
> 
> 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 :-)
> 
> If it's an easy win I'd be willing to do it.  I'm not the world's greatest 
> C hacker, but I still remember enough of it to be competant.

Yea, I guess we could.  I think the consensus is that the uppercase
default is so weird, we don't know anyone who would want to use it. 
Would you?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026