> > As the same column, actually ... you know: case insensitive, but case
> > preserving.
>
> If I understand correctly, preserving the case is really important only
> for tools.

Dunno if it's really for tools, or just for DDL that people want to see
extracted.

>Possibly, during the Vulcan merge, we could add another
> field to the system tables (relations, fields, rfr, triggers,
> procedures, indicies, etc.)called something like RDB$PREFERRED_CASE
> which would hold the name as originally entered. Unfortunately,
> changing the RDB$xxx_NAME fields to hold the original representation is
> problematic since the Borland engineers decided not to add a specific
> indication for delimited identifiers, but to recognize that any name
> with special characters (e.g. lower case, spaces, etc.) must be a
> delimited identifier.

Yep. And that's a true pain...

>If a separate field would work, that's not a big
> deal.

What would the sequence be then?

-> if pref_case = normal_name and normal_name does not include
special characters, use pref_case

-> if normal_name includes specials, use delimited

-> else use normal_name

?

With regards,

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