From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Grzegorz Szpetkowski <gszpetkowski(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Feature idea: standard_quoting_identifiers property |
Date: | 2011-06-10 13:03:04 |
Message-ID: | 4DF21608.2040401@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10.06.2011 13:06, Grzegorz Szpetkowski wrote:
> 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) ?
This has been suggested and rejected, or at least left unresolved
because no-one has been able to figure out all the details, many times
before. You should read the past discussions on this. For starters, see
the list of threads listed on the TODO item on this:
http://wiki.postgresql.org/wiki/Todo
"Consider allowing control of upper/lower case folding of unquoted
identifiers"
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-06-10 14:20:05 | Re: [BUG] Denormal float values break backup/restore |
Previous Message | Gurjeet Singh | 2011-06-10 11:34:27 | Re: Creating new remote branch in git? |