On Mon, Nov 26, 2001 at 01:02:53PM -0800, Nate Gelbard wrote:
>
> > of a complaint on how SQL is case insensitive and if you have created
> > your objects with quoted mixed case identifiers you need to accessthem
> > via quoted mixed case identifiers. I haven't seen any evidence that
>
> I am mistaken. This is actually a bug in the applications that are
> building SQL statements without quotes around tablenames of mixedcase.
Bad apps are everywhere. I've met quite a few that make the Oracle assumption
about casefolding: MixedCase == MIXEDCASE i.e. Oracle upcases everything.
The other place you'll hit this is NTFS (i.e. NT file system): names are
casepresevering but _not_ case sensitive, so MixEdCase == MIXEDCASE ==
mixecase all conflict, but will be stored (and returned) however the
app. (or user) spelled it the first time. Another example of being overly
helpful.
Ross