Subject | Re: [firebird-support] Use of double quoted names in Firebird |
---|---|
Author | Ann W. Harrison |
Post date | 2005-03-17T21:59:08Z |
Uwe Grauer wrote:
when creating definitions if the input isn't typed in ALL UPPER CASE.
They're part of the SQL standard and intended to bridge the different
usages of different database systems. (Actually, probably mostly the
individual quirks of the writers of SQL parsers.) The good uses for
quoted identifiers are to allow the use of key words in object names, to
allow spaces in object names, and to allow characters other than a-z,
A-Z, 0-9, $, and # in names. All those are primarily for compatibility
with other databases. A really perverse use is to allow the same word
to represent different objects with different capitalization.
Regards,
Ann
> This question came up for me in another mailing-list.To deal with database created by tools that automatically quote names
> What is the most used way to use double quoted names in FB?
when creating definitions if the input isn't typed in ALL UPPER CASE.
> And WHY is it the way it is?Confusion.
> Personally im always do not use double quotes for names because otherwiseGood plan.
> im forced to remember the case or i have to be really careful with
> case-different names.
> Maybe there were some backward compatibility issues introducing this?Quoted identifiers were added in InterBase 6 as part of Dialect 3.
> Please tell me the history of double quoted names in FB.
They're part of the SQL standard and intended to bridge the different
usages of different database systems. (Actually, probably mostly the
individual quirks of the writers of SQL parsers.) The good uses for
quoted identifiers are to allow the use of key words in object names, to
allow spaces in object names, and to allow characters other than a-z,
A-Z, 0-9, $, and # in names. All those are primarily for compatibility
with other databases. A really perverse use is to allow the same word
to represent different objects with different capitalization.
Regards,
Ann