Re: Runtime Config Option for identifier case preservation - Mailing list pgsql-patches

From Michael W Mitton
Subject Re: Runtime Config Option for identifier case preservation
Date
Msg-id 200501141510.31166.mmitton@ssi-c.com
Whole thread Raw
In response to Runtime Config Option for identifier case preservation  (Michael W Mitton <mmitton@ssi-c.com>)
List pgsql-patches
Opps!  I have my logic backwards below.  Those two SQL sets should be
set parser-ignore-case = true;
select "Address_id" from "Address";

set parser-ignore-case = false;
select Address_id from Address;


On Friday 14 January 2005 02:51 pm, Michael W Mitton wrote:
> Attached is a patch to allow the user to change the behavior of postgres
> with reguards to case sensitivity on unquoted identifiers.  This does not
> change the default behavior of converting unquoted identifiers to
> lowercase, but does allow (for instance, and I'm absolutly -not- pulling
> from personal experience here <g>) a large project to run under postgres
> that did run under MySQL a whole bunch easier.
>
> for example, these two SQL statements sets are identical
> set parser-ignore-case = false;
> select "Address_id" from "Address";
>
> set parser-ignore-case = true;
> select Address_id from Address;

pgsql-patches by date:

Previous
From: Michael W Mitton
Date:
Subject: Runtime Config Option for identifier case preservation
Next
From: Tom Lane
Date:
Subject: Re: Runtime Config Option for identifier case preservation