views:

155

answers:

2

I am running ActiveState's ActivePython 2.6.5.12 and PostgreSQL 9.0 Beta 1 under Windows XP.

If I create a table with an upper case first letter (i.e. Books), psycopg2 returns the "Programming Error: relation "books" does not exist" error message when I run the select statement: execute("SELECT * FROM Books"). The same error is returned if I run: execute("SELECT * FROM books"). However, if I change the table to a lower case first name (i.e. books), then either of the above statements works.

Are tables name supposed to have a lower case first name? Is this a setting or a feature or a bug? Am I missing something obvious?

+1  A: 

Read "Identifiers and Key Words" from the manual, especially the part about "quoted identifiers".

Milen A. Radev
Huzzah! So "execute('SELECT * FROM "Books"') works. And since I also capitalize my column names, I have to use "execute('SELECT "Title" FROM "Books"').Is it the "standard" or accepted method to always use lower cases table and field names in PostgreSQL databases?
Count Boxer
Writing all identifiers in lower case (and separating words with underscore) is a kind of convention, mostly for convenience. Regarding the so-called "case-folding" by the parser - the SQL standard dictates such behaviour (with one difference - when unquoted the identifiers are folded to upper-case).
Milen A. Radev
Quoting identifiers is something MSSQL developers seem to have a penchant for. But most other database developers tend not to do that. If you don't quote the identifiers when creating the tables, views, functions then you don't have to worry about quoting them later. If you don't quote, Postgres will fold to lower case while Oracle will do upper case.
Scott Bailey
A: 

To add to the other answer, the behaviour of Postresql about case-sentivity of identifiers (table names and column names) is :

  • If the name is not quoted, it is converted to lowercase. Otherwise, it's left untouched.
  • Afterwards, a case sensitive match is attempted.

This applies not only for queries, but also for schema manipulation; in particular: table creation.

The rule of gold is consistency:

If you want to write portable applications you are advised to always quote a particular name or never quote it

The posted problem arose, probably, because the tables and columns names were quoted at creation time (hence, they were not converted to lowercase). So, now they must be quoted (and case-sensitive) in all queries.

Normally, all works ok.

db=# create table Xxx (id integer); -- unquoted, will be converted to lowercase
CREATE TABLE
db=# select * from xXx;    -- this works ok
id
----
(0 rows)
db=# create table "Xxxx" (id integer);  -- will be left untouched
CREATE TABLE
db=# select * from xxxx;                -- bad
ERROR:  relation "xxxx" does not exist
LINE 1: select * from xxxx;
db=# select * from Xxxx;                -- bad
ERROR:  relation "xxxx" does not exist
LINE 1: select * from Xxxx;
^
db=# select * from "Xxxx";               -- ok
id
----
(0 rows)

db=# \dt *xx*
List of relations
Schema | Name | Type  |  Owner
--------+------+-------+----------
public | Xxxx | table | postgres
public | xxx  | table | postgres
leonbloy