| From: | Michael W Mitton <mmitton(at)ssi-c(dot)com> | 
|---|---|
| To: | pgsql-patches(at)postgresql(dot)org | 
| Subject: | Re: Runtime Config Option for identifier case preservation | 
| Date: | 2005-01-14 20:10:31 | 
| Message-ID: | 200501141510.31166.mmitton@ssi-c.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | 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;
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-01-14 21:47:52 | Re: Runtime Config Option for identifier case preservation | 
| Previous Message | Michael W Mitton | 2005-01-14 19:51:08 | Runtime Config Option for identifier case preservation |