Martijn Tonies wrote:

>
> 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. 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. If a separate field would work, that's not a big
deal.

Regards,


Ann