MichaelS wrote:

> Finally, maybe, since I'm probably not the only person that has a
> strong pref for mixed cases, could this be considered for a future
> version of firebird? I guess it's a priority to keep C programmers
> happy with the look and feel of firebird objects (per Helen), but
> couldn't there be an option, a switch that'd allow a developer to
> choose the approach to take with regards to object name case? Is is
> really a big deal to offer such, or is it just uninteresting because
> all uppercase is more compliant with SQL 92 (or whatever it is)?

We recently had a huge discussion on this subject in conjunction with
the issue of national characters.

I think the consensus (well...) was:

- For unquoted identifiers, store the names in uppercase but ignore case
whenever the identifier is used. Also, only allow plain 7 bit ascii.

- For quoted identifiers, store the names as specified. Case will be
significant when the identifier is used. Also, allow all(?) unicode
characters in the identifier.

Anything else will cause problems.

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