Received: from localhost (maia-1.hub.org [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id 6F9229F9F7B
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Sat,  2 Dec 2006 12:48:45 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024)
	with ESMTP id 66350-05 for <pgsql-sql-postgresql.org@postgresql.org>;
	Sat,  2 Dec 2006 12:48:42 -0400 (AST)
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 E7CA19F9429
	for <pgsql-sql@postgresql.org>; Sat,  2 Dec 2006 12:48:40 -0400 (AST)
Received: from 192.168.0.6 by www01.kensystem.com (SMTPD);
	id s20061202164838.74075; Sat, 02 Dec 2006 16:48:38
Message-ID: <4571AE66.7050304@kensystem.com>
Date: Sat, 02 Dec 2006 09:48:38 -0700
From: Ken Johanson <pg-user@kensystem.com>
Reply-To: ken@kensystem.com
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Dennis Bjorklund <db@zigo.dhs.org>
CC: Martijn van Oosterhout <kleptog@svana.org>,  pgsql-sql@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>
	<457199E4.3010401@kensystem.com> <4571A3AF.6070608@zigo.dhs.org>
In-Reply-To: <4571A3AF.6070608@zigo.dhs.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/27
X-Sequence-Number: 26983

Dennis Bjorklund wrote:
> Ken Johanson skrev:
> 
>> Has your experience with PG been different? If so I presume you have 
>> have found a config that allows?:
>>
>> SELECT
>> pers.firstName,
>> pers.lastname,
> 
> As long as you don't create the columns using quotes you can use that 
> kind of names. For example
> 
>   CREATE TABLE foo (BAR int);
> 
>   INSERT INTO foo VALUES (42);
> 
>   SELECT BaR, bar, BAR, "bar" FROM foo;
> 
> But using "Bar" wont work.
> 
> /Dennis
> 

That definitely makes sense. If one *wants* to enforce case, they should 
create the identifier with quotes.

Although, since I'm using pgAdmin (III) to design tables in this case, 
or creating the tables through JDBC (a convenient way to copy tables and 
data from another datasource) (using the copy-paste gesture), I believe 
those tools both *are* quoting identifiers that have camel case. And 
that their behavior can't be overridden.

So though I might personally be comfortable with DDL commands to 
re-define my existing quoted columns (as created by JDBC and pgAdmin), 
other users may not be. And having to recreate and issue the DDL to use 
un-quoted col names will be tedious in my case since I have ~20 tables 
to import.

So my vote would remain for having a config-option to ignore case, even 
on quoted identifiers..

Ken