Subject | Re: [firebird-support] Re: Error -104 on SELECT |
---|---|
Author | Paul Vinkenoog |
Post date | 2011-02-06T17:13:10Z |
Tim Seyfarth wrote:
- If you define them without quotes, they are stored in all-uppercase. In queries, you can refer to them:
* unquoted in upper, lower or mixed case: MyColumn, mycolumn, MYCOLUMN...
* quoted in all-uppercase: "MYCOLUMN".
- If you define them within quotes, they are stored as-is, and you can refer to them:
* within quotes in the exact same case;
* only for names defined in all-uppers and without funny characters: without quotes in upper, lower or mixed case.
Unless you have a compelling reason, you save yourself a lot of headaches if you define your objects case-insensitively (without quotes).
HTH,
Paul Vinkenoog
> What of the field/column names? Should they also be upper case for FB?For (almost) all database object names - including tables and columns, the rules are:
- If you define them without quotes, they are stored in all-uppercase. In queries, you can refer to them:
* unquoted in upper, lower or mixed case: MyColumn, mycolumn, MYCOLUMN...
* quoted in all-uppercase: "MYCOLUMN".
- If you define them within quotes, they are stored as-is, and you can refer to them:
* within quotes in the exact same case;
* only for names defined in all-uppers and without funny characters: without quotes in upper, lower or mixed case.
Unless you have a compelling reason, you save yourself a lot of headaches if you define your objects case-insensitively (without quotes).
HTH,
Paul Vinkenoog