Subject | Re: [firebird-support] Re: Upper case behaviour |
---|---|
Author | Geoff Worboys |
Post date | 2007-12-05T00:21:50Z |
Hi Adam,
identifiers in SQL statements, such as selects - and in such
cases you need to identify the specific object (use its
actual name or something uniquely translatable to its name).
If I have misunderstood and all that is required is a display
name then I guess that is for the developers to respond. It
does not worry me, but I can see where it may be a problem for
someone transfering from a dbms that preserved case.
I suspect it does not stay simple... if the system does not
insist that the display name is unique (within context) then
the returned information becomes ambiguous. If the display
name is not the same as the actual name then you will need to
ensure that tools/options are available to retrieve the
actual names too - so that it is easy to discover the actual
names for writing of SQL statements.
--
Geoff Worboys
Telesis Computing
> I think we are complicating the issue beyond what the OP isIt seemed to me that the query was relating to the use of
> asking for. All Firebird really needs to do to support such
> a feature is add a few fields in the various system tables
> to store the text as declared
> eg. RDB$RELATIONS.RDB$RELATION_NAME can have a sister field
> RDB$RELATIONS.RDB$RELATION_DISPLAYNAME
> The case sensitivity, delimiter rules and stored field names
> remain unchanged, but third party tools (as well as Show
> Tables etc) can report the display name.
identifiers in SQL statements, such as selects - and in such
cases you need to identify the specific object (use its
actual name or something uniquely translatable to its name).
If I have misunderstood and all that is required is a display
name then I guess that is for the developers to respond. It
does not worry me, but I can see where it may be a problem for
someone transfering from a dbms that preserved case.
I suspect it does not stay simple... if the system does not
insist that the display name is unique (within context) then
the returned information becomes ambiguous. If the display
name is not the same as the actual name then you will need to
ensure that tools/options are available to retrieve the
actual names too - so that it is easy to discover the actual
names for writing of SQL statements.
--
Geoff Worboys
Telesis Computing