Alexandre Benson Smith wrote:

> If you put the table name (or other identifier) enclosed on quotes, you
> SHOULD use it everywhere with the quotes and with the same case, if you
> don't use quotes the identififer will be case insensitive.

Some (most?) tools don't fully support mixed case, even in quoted names.

For example, if you use a quoted table name in FlameRobin (a client
tool) to create a table:

create table "MyTable" ...

then FlameRobin will parse this SQL and list the table's name in
uppercase in its list of tables. But if you disconnect and reconnect,
it's listed with the proper case.

There are other problems too.

While I personally feel strongly about using quoted names and mixed
case, you should do so only if you are confident that it won't cause
problems due to lacking support in your tools, tiers, API:s etc.

Currently, the best way to avoid problems is to drop quotes and use all
uppercase for all names everywhere, and only use plain (7 bit) ASCII.

Good luck!
Kjell
--
--------------------------------------
Kjell Rilbe
Adressmarknaden AM AB
E-post: kjell.rilbe@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64