From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Алексей Бережняк <core(at)irc(dot)lg(dot)ua> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Correct place for feature requests |
Date: | 2015-06-29 14:49:26 |
Message-ID: | CAHyXU0yGJxuu2hfUOfqDakz9Fu7-U+B7mGjWppEu4oPDdLMF1A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jun 25, 2015 at 1:59 PM, Алексей Бережняк <core(at)irc(dot)lg(dot)ua> wrote:
> I think that PostgreSQL is great RDBMS, but one important (for me)
> feature that it missing is case-insensitive identifier quotes
> ([table].[column]) like in Microsoft SQL Server.
>
> I know that there are double quotes, but they are case-sensitive.
>
> Or maybe some option that will make double quotes case-insensitive.
This behavior is not going to change because of having to support
decades of code written around the current set of rules. SQL Server
is very much in the same boat having inherited its somewhat quixotic
casing rules. SQL server's semantics are not SQL standard anyways so
even if postgres did change it would not be in that direction. SQL
server is basically fully case insensitive while postgres is case
sensitive (but works around this to some extent via case folding).
It's really somewhat of a shame, but to write portable SQL you want to
name_identifiers_like_this (particularly with postgres due to case
folding) and completely avoid syntax that requires identifier quoting.
Also stay away from keywords or anything that might become one.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Arthur Silva | 2015-06-29 15:23:10 | Re: Which replication is the best for our case ? |
Previous Message | Adrian Klaver | 2015-06-29 13:58:50 | Re: Need for re-index after pg_upgrade |