|
1 | 1 |
|
2 | 2 | Frequently Asked Questions (FAQ) for PostgreSQL
|
3 | 3 |
|
4 |
| - Last updated: Thu Sep 27 02:14:24 EDT 2007 |
| 4 | + Last updated: Mon Oct 8 23:19:46 EDT 2007 |
5 | 5 |
|
6 | 6 | Current maintainer: Bruce Momjian (bruce@momjian.us)
|
7 | 7 |
|
|
840 | 840 | 4.21) Why are my table and column names not recognized in my query? Why is
|
841 | 841 | capitalization not preserved?
|
842 | 842 |
|
843 |
| - The most common cause of recognized names is the use of double-quotes |
844 |
| - around table or column names during table creation. When double-quotes |
845 |
| - are used, table and column names (called identifiers) are stored |
846 |
| - case-sensitive, meaning you must use double-quotes when referencing |
847 |
| - the names in a query. Some interfaces, like pgAdmin, automatically |
848 |
| - double-quote identifiers during table creation. So, for identifiers to |
849 |
| - be recognized, you must either: |
| 843 | + The most common cause of unrecognized names is the use of |
| 844 | + double-quotes around table or column names during table creation. When |
| 845 | + double-quotes are used, table and column names (called identifiers) |
| 846 | + are stored case-sensitive, meaning you must use double-quotes when |
| 847 | + referencing the names in a query. Some interfaces, like pgAdmin, |
| 848 | + automatically double-quote identifiers during table creation. So, for |
| 849 | + identifiers to be recognized, you must either: |
850 | 850 | * Avoid double-quoting identifiers when creating tables
|
851 | 851 | * Use only lowercase characters in identifiers
|
852 | 852 | * Double-quote identifiers when referencing them in queries
|
0 commit comments