| Subject | Re: [firebird-support] Use of double quoted names in Firebird |
|---|---|
| Author | Alexandre Benson Smith |
| Post date | 2005-03-17T20:58:52Z |
Uwe Grauer wrote:
Quotted Identifiers are case sensitive (I think SQL standard requires
it), and I think the only reasonable use is when you want to use
reserved words as a identifier name.
Quoted Identifiers are not recommended by the majority of the users for
the reasons you have exposed, and you will need to put the quotes
everytime, IMO it just make a statement hard to read.
If for example you have in your DB a column that uses a word ("case"
for example) that was not reserved in the past, but turns a reserved
word on newer FB version you will need to use quoted identifier if you
want to continue to use that name, but it will require that you rewrite
your query in any case to add the quotes, if you always use quoted
identifiers, even if a new reserved word is introduced, that will not
affect your query. I rarely hit this case, since my column names are in
Portuguese (the cases where a portuguese word is equal to an english
word and that english word is a reserved word is very rare) I think
english users hit this case very often, when I got in this situation I
try to find a synonym for that word or use an abreviation or append the
tablename, or something similar, I never used quotted identifier, and If
I were you I will avoid this too :-)
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda.
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.3 - Release Date: 15/03/2005
>This question came up for me in another mailing-list.I will tell what I think, maybe I am completely wrong.... :-)
>What is the most used way to use double quoted names in FB?
>And WHY is it the way it is?
>Personally im always do not use double quotes for names because otherwise
>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?
>Please tell me the history of double quoted names in FB.
>
>Regards,
> Uwe
>
>
Quotted Identifiers are case sensitive (I think SQL standard requires
it), and I think the only reasonable use is when you want to use
reserved words as a identifier name.
Quoted Identifiers are not recommended by the majority of the users for
the reasons you have exposed, and you will need to put the quotes
everytime, IMO it just make a statement hard to read.
If for example you have in your DB a column that uses a word ("case"
for example) that was not reserved in the past, but turns a reserved
word on newer FB version you will need to use quoted identifier if you
want to continue to use that name, but it will require that you rewrite
your query in any case to add the quotes, if you always use quoted
identifiers, even if a new reserved word is introduced, that will not
affect your query. I rarely hit this case, since my column names are in
Portuguese (the cases where a portuguese word is equal to an english
word and that english word is a reserved word is very rare) I think
english users hit this case very often, when I got in this situation I
try to find a synonym for that word or use an abreviation or append the
tablename, or something similar, I never used quotted identifier, and If
I were you I will avoid this too :-)
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda.
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.3 - Release Date: 15/03/2005