Subject | RE: [IBO] IBO 4.8.7 to IBO 5.2.0 6 |
---|---|
Author | Helen Borrie |
Post date | 2013-06-14T01:06:43Z |
At 10:22 a.m. 14/06/2013, IBO Support List wrote:
I have noticed that IB_SQL, for some longish time, is automatically double-quoting some identifiers in a database of mine that started life as ODS 10.1, where the names were not keywords. I have never figured out whether that is just a trick of IB_SQL or whether it is actually happening in the IB_Statement processing. Because these identifiers are defined in upper case, it causes no problems whatsoever.
And no, don't use column aliases for real columns unless you have *no other choice*. They are not intended for that usage and they'll kill performance. It's a bit of a bind to have to go back and fix up those double-quoted columns but it's a do-once and once it's done, it's done for good.
Helen
>When you put a name inside of double quotes then it becomes case sensitive.Yes, I would *not* recommend defining columns that use quoted keywords as case-sensitive. Define them in upper case and, in some conditions, they will work if used unquoted.
I have noticed that IB_SQL, for some longish time, is automatically double-quoting some identifiers in a database of mine that started life as ODS 10.1, where the names were not keywords. I have never figured out whether that is just a trick of IB_SQL or whether it is actually happening in the IB_Statement processing. Because these identifiers are defined in upper case, it causes no problems whatsoever.
And no, don't use column aliases for real columns unless you have *no other choice*. They are not intended for that usage and they'll kill performance. It's a bit of a bind to have to go back and fix up those double-quoted columns but it's a do-once and once it's done, it's done for good.
Helen