Forgive me if there was already some discussion about it (I can't find anyone). As documentation describes (http://www.postgresql.org/docs/9.1/static/sql-syntax-lexical.html):
"Quoting an identifier also makes it case-sensitive, whereas unquoted names are always folded to lower case. For example, the identifiers FOO, foo, and "foo" are considered the same by PostgreSQL, but "Foo" and "FOO" are different from these three and each other. (The folding of unquoted names to lower case in PostgreSQL is incompatible with the SQL standard, which says that unquoted names should be folded to upper case. Thus, foo should be equivalent to "FOO" not "foo" according to the standard. If you want to write portable applications you are advised to always quote a particular name or never quote it.)" What do you think about adding new postgresql.conf property, let's briefly say standard_quoting_identifiers with default value off to maintain backward compatibility, which allows to use standard upper-case equivalents (so Foo and "FOO" will be the same, but Foo and "foo" not) ? Pros (that I see): -- SQL standard conformance -- easier migration from/to other RDBMS like Oracle DB Regards, Grzegorz Szpetkowski -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
