X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id B85E39DC9F4
	for <pgsql-general-postgresql.org@localhost.postgresql.org>;
	Tue, 27 Dec 2005 11:14:16 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 37074-03
	for <pgsql-general-postgresql.org@localhost.postgresql.org>;
	Tue, 27 Dec 2005 11:14:21 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from worleyco.com (unknown [70.158.54.226])
	by postgresql.org (Postfix) with ESMTP id 959DF9DC9C8
	for <pgsql-general@postgresql.org>;
	Tue, 27 Dec 2005 11:14:14 -0400 (AST)
Received: from [192.168.4.11] (unknown [192.168.4.11])
	by worleyco.com (Postfix) with ESMTP id 2A2A815E0A0;
	Tue, 27 Dec 2005 10:03:59 -0600 (CST)
Message-ID: <43B15A4C.9040809@hardgeus.com>
Date: Tue, 27 Dec 2005 09:14:20 -0600
From: John McCawley <nospam@hardgeus.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dfx@dfx.it
Cc: pgsql-general@postgresql.org
Subject: Re: Case sensitivity?
References: <000501c60b40$ea790510$fc00a8c0@dfx>
In-Reply-To: <000501c60b40$ea790510$fc00a8c0@dfx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.806 required=5 tests=[AWL=-0.806,
	DEAR_SOMETHING=1.612]
X-Spam-Score: 0.806
X-Spam-Level: 
X-Archive-Number: 200512/1177
X-Sequence-Number: 88740

Due to case weirdness in Postgres, particularly when accessing it from 
PHP, I completely abandoned mixed case table and column names.  I don't 
know if things have changed in the past several years, but when I first 
made the leap, mixed case was more trouble than it was worth.

Even after I got over the initial hump and figured out how to make it 
work, there was enough weird behavior (i.e. being able to access a 
non-existent array element) in PHP that it led to a lot of bugs when 
using mixed-case in Postgres.  That's my two cents.  Your mileage may 
vary...

dfx wrote:

> Dear Sirs,
> <snip> 
> please note the change of the case of "A" to "a";
>  
> if I rename the table to "accoglienza" the error disappear, but arise 
> another error on "IdAccoglienza" that change in "idaccoglienza". (i.e. 
> all converted to lower case)
>