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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
