Received: from mail1.ihs.com (mail1.ihs.com [170.207.70.222])
	by postgresql.org (Postfix) with ESMTP
	id 70CCF47511A; Fri, 19 Jul 2002 13:07:59 -0400 (EDT)
Received: from css120.ihs.com (css120.ihs.com [170.207.105.120])
	by mail1.ihs.com (8.12.4/8.12.4) with ESMTP id g6JH6Zbc001642;
	Fri, 19 Jul 2002 11:06:35 -0600 (MDT)
Date: Fri, 19 Jul 2002 10:53:50 -0600 (MDT)
From: "scott.marlowe" <scott.marlowe@ihs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: stefan@extum.com, Martijn van Oosterhout <kleptog@svana.org>,
	<pgsql-sql@postgresql.org>, <pgsql-general@postgresql.org>
Subject: Re: [SQL] id and ID in CREATE TABLE 
In-Reply-To: <12220.1027085465@sss.pgh.pa.us>
Message-ID: <Pine.LNX.4.44.0207191051550.3990-100000@css120.ihs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-MailBodyFilter: Message body has not been filtered
X-MailScanner: Found to be clean
X-Archive-Number: 200207/1231
X-Sequence-Number: 27718

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.