[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] Allow disabling folding of unquoted identifiers to lowercase
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2016-04-29 23:31:11
Message-ID: 31857.1461972671 () sss ! pgh ! pa ! us
[Download RAW message or body]

John McKown <john.archie.mckown@gmail.com> writes:
> ​Oh well, it's been interesting, but I don't think that we'll come to a
> resolution for the OP on this issue. I just blame both PostgreSQL and MySQL
> for this problem because the SQL standard says that the names are
> automatically UPPERCASEd unless enclosed in quotes. Not lower cased as
> PostgreSQL does it, nor unchanged as MySQL does it.​

Yeah, this isn't going to happen.  Years ago we looked into what it would
take to be able to flip a switch and have the standard-compliant behavior
(fold to upper not lower).  It was impractical then and no doubt is far
more so now.  I do not remember all the details, but there were multiple
pain points even in terms of server-side implementation, never mind all
the applications we'd break.

What the OP is asking for doesn't even have the argument "but it's
standards compliant!" going for it.  So I doubt we'd accept such a patch
even if someone managed to create one.

			regards, tom lane


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[prev in list] [next in list] [prev in thread] [next in thread]