Martijn van Oosterhout <kleptog@svana.org> writes:
> The main problem I see is that the most people who are complaining are
> people who create their tables as "MixedCaseQuoted" and then refer to
> them as Unquoted. Even following the SQL standard precisely will not
> fix this, given that behaviour is non-standard also.
> Seems to me we'd be better off creating an option
> "lowercase_quoted_anyway" which solves everything, at the expense of
> being even less compliant.
Hmm. That solves the problem for people who are used to MySQL or Access
or whatever it is that behaves like that, but that problem hasn't really
been on the radar screen that I've noticed. The push-back I've been
paying attention to is from people who say "this application expects the
standard-mandated behavior, why aren't you following the standard?"
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.
Comments anyone?
regards, tom lane