Re: Allow disabling folding of unquoted identifiers to lowercase

On 30 April 2016 at 01:31, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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.
>

Alright, thanks to everyone for looking into this. Not knowing the code, I
naively assumed it should be easy to add an option to not do the case
folding.

>
> What the OP is asking for doesn't even have the argument "but it's
> standards compliant!" going for it.
>
> Indeed, my argument was it would allow people to choose their own naming
convention to (easily) use with Postgres, which would in turn make it
easier to migrate from other RDBMSes to Postgres. Although, if you want a
standard compliance argument, that can easily be added. :) Just have 3
options: fold to lowercase (current behaviour, default), fold to uppercase
(standards compliant), do not fold (most flexible, compatible with MSSQL
and MySQL).

> So I doubt we'd accept such a patch even if someone managed to create one.

Well, I was going to ask if paying someone to fix this was an option, but
this preempts that!