> >
> >As I see it, the problem is that when a person who doesn't have English
> >as his native toungue, he has to do some kind of translation between the
> >name he actually wants and the name he can use. This translation has to
> >follow some kind of standard.
>
> It's my case also, my native tongue is Portuguese. Is very rich in
> various types of accents. And no, I don't use quoted identifiers with
> accents
> or mixed case.
>
> >
> >In your examples, you've apparently chosen not to translate the words to
> >English but simply strip them of accents and convert them to uppercase.
>
> Yes. Works like a charm. And without the hassles of quoted identifiers.
> So I can query it as:
>
> select * from Clientes
> select * from ClIeNtEs
> Select * from clientes
> Select * from CLIENTES
> etc.
> etc.
> etc.
> All of them are valid queries...

As I said - the problem with MS SQL arises when you do

FROM CLIENTES while it was created as clientes and the
uppercase "i" to "I" isn't the right one. There are languages
where this happens! Apparently, the engine compages the
written query _directly_ to what's in its system tables.


If the Firebird implementation would be better, this might
be a moot point.

With regards,

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