> >>Why should SQL stay behind?
> >
> > Well... for one...
> >
> > In SQL Server, there was this system table INDEXES. It was
> > defined as "indexes". Guess what happens on a server with a
> > Turkish collation as the server wide collation?
> >
> > indexes uppercased becomes ÍNDEXES because the small
> > character "i" becomes "Í" and not "I".
> >
> > Now, this means that every metadata name, although defined
> > as "indexes" (no quotes, not case sensitive) might get messed
> > up because of national crap.
>
> On the other hand, since quoted identifiers are case sensitive, this
> wouldn't be a problem.

I wasn't talking about quotes, I was talking about nationalization.

:-)

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com