Subject | Re: [firebird-support] Upper case behaviour |
---|---|
Author | Nando Dessena |
Post date | 2007-12-04T16:26:05Z |
Woody,
W> Camel case is a preference and although it looks good to you and to me, many
W> people prefer all upper or lower case. You aren't asking for anything new,
W> but I believe in order to follow SQL standards, once you quote a table/field
W> name, you must always quote it. Someone more knowledgable can correct that
W> to whatever the standard is but it makes sense to me.
The OP is just asking for Firebird to stay case-insensitive but become
case-preserving, meaning it will spit out whatever case was used
during definition. This can be done without breaking the SQL standard
(SQL Server is a good example), but I guess it would be a very
pervasive change to Firebird's code base. Too much to be considered.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================
W> Camel case is a preference and although it looks good to you and to me, many
W> people prefer all upper or lower case. You aren't asking for anything new,
W> but I believe in order to follow SQL standards, once you quote a table/field
W> name, you must always quote it. Someone more knowledgable can correct that
W> to whatever the standard is but it makes sense to me.
The OP is just asking for Firebird to stay case-insensitive but become
case-preserving, meaning it will spit out whatever case was used
during definition. This can be done without breaking the SQL standard
(SQL Server is a good example), but I guess it would be a very
pervasive change to Firebird's code base. Too much to be considered.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================