Table structure is NOT for end users. SQL is NOT for
end users. Database structure is NOT for end users.

Only DATA is for end users. The one thing that's
interest them, presented in a nice front-end.

In the front-end you show the information that is needed,
searched the way that they need it, showed in the form
they need it.

Accent-sensitive table names? ARRRRRRRRRGHHHHHHHH!
I have enough trouble with the column names I return to
the other systems in the project I am DBA.

On Sat, 19 Mar 2005 17:14:20 +0100, Kjell Rilbe wrote:

>
>The computerized world is constantly moving towards support for
>nationalization. Unicode is spreading. You can now actually use national
>characters in domain names (but you have to back them up with plain
>ASCII versions due to old browsers etc.). Most applications that target
>"normal users" have nationalized versions. Even Delphi comes in three
>language versions and that's a development too.
>
>Why should SQL stay behind?
>
>Kjell
>
>Fabricio Araujo wrote:
>> National characters on (for example) in table names?
>> Hmmmm... No. Even in MSSQL I didn't use it, except for
>> column titles in queries. And even that past decision
>> I don't like.
>> For me, quotes is a crap feature of SQL Standard.
>> I have enough headaches, I don't need a new source...
>--
>--------------------------------------
>Kjell Rilbe
>Adressmarknaden AM AB
>E-post: kjell.rilbe@...
>Telefon: 08-761 06 55
>Mobil: 0733-44 24 64
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>