Received: from localhost (maia-2.hub.org [200.46.204.187])
	by postgresql.org (Postfix) with ESMTP id 39CCF9F9EED;
	Sat,  2 Dec 2006 11:21:22 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024)
	with ESMTP id 47555-08; Sat,  2 Dec 2006 11:21:07 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from www01.kensystem.com (www01.kensystem.com [72.19.170.120])
	by postgresql.org (Postfix) with ESMTP id E7E2D9F9429;
	Sat,  2 Dec 2006 11:21:12 -0400 (AST)
Received: from 192.168.0.3 by www01.kensystem.com (SMTPD);
	id s20061202152108.73960; Sat, 02 Dec 2006 15:21:08
Message-ID: <457199E4.3010401@kensystem.com>
Date: Sat, 02 Dec 2006 08:21:08 -0700
From: Ken Johanson <pg-user@kensystem.com>
Reply-To: ken@kensystem.com
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Martijn van Oosterhout <kleptog@svana.org>
CC: pgsql-sql@postgresql.org,  pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Case Preservation disregarding case
References: <200610271623.37525.beauh@bluefrogmobile.com>
	<1162003132.687.8.camel@pampa>
	<200610301928.51255.beauh@bluefrogmobile.com>
	<23177.1162265010@sss.pgh.pa.us>
	<EB48EBF3B239E948AC1E3F3780CF8F88012F88DD@MI8NYCMAIL02.Mi8.com>
	<45712E31.1030004@kensystem.com> <20061202133556.GC26365@svana.org>
In-Reply-To: <20061202133556.GC26365@svana.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200612/25
X-Sequence-Number: 26981

Martijn van Oosterhout wrote:
> On Sat, Dec 02, 2006 at 12:41:37AM -0700, Ken Johanson wrote:
>> 1: It seems like this behavior of case sensitive-or-not-identifiers 
>> could/should be a config option -- either globally for the server, 
>> database, or at the connection/session level. Other databases *do* 
>> support this type of granular config of misc SQL behavior -- its 
>> essential for shared hosting environments. Without it some users just 
>> *cant* make the switch. Quoting all an app's identifiers -- or renaming 
>> camel-case to underscored -- show stopper.
> 
> What about option 3: use camelcase without underscares and don't quote.
> Then you get case-insensetivity and it's still readable.
> 
> You're obviously talking about an app which isn't quoting identifiers,
> so I'm not sure what the actual problem is.
> 
> Have a nice day,

Yes, I do routinely use non-quoted identifiers. The problem is, that 
they are case-folded (to lower in PG's case), so my camel-case does not 
match. For the query to work I MUST quote identifiers hat have camel-case.

SELECT
pers."firstName",
pers.lastname,
...

Has your experience with PG been different? If so I presume you have 
have found a config that allows?:

SELECT
pers.firstName,
pers.lastname,

Ken