| From: | Matthew <matthew(at)zeut(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Chris Travers <chris(at)travelamericas(dot)com>, Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "Aly S(dot)P Dharshi" <aly(dot)dharshi(at)telus(dot)net>, "Gavin M(dot) Roy" <gmr(at)ehpg(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Gotchas |
| Date: | 2005-10-16 17:29:26 |
| Message-ID: | 43528DF6.4080106@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Although ... it's true that there seem to be very few apps relying on
> case sensitivity per se, ie, expecting "Foo" and "foo" to be different.
> The complaints that I can remember were about programs that expected
> "FOO" and FOO (not quoted) to be the same. So always-smash-to-lower-
> case might indeed solve most of the real-world problem for the Oracle
> camp as well.
Is it worth having a GUC variable that enables / disable this? I hate
to add GUCs but this seems like a fairly significant change in expected
behavior. Not sure it's a good idea, but I thought I should ask the
question anyway.
Matt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-10-16 17:37:56 | Re: PostgreSQL Gotchas |
| Previous Message | Martijn van Oosterhout | 2005-10-16 17:15:15 | Re: PostgreSQL Gotchas |