Re: quoted identifier behaviour

Randall Smith <randall(at)tnr(dot)cc> writes:
> I'm an advocate of Postgresql and usually tout SQL compliance as a
> strength, so it bothers me that this is not in line to be corrected.

It's not that it's not on the radar screen, it's just that no one sees
a way to do it that's going to be acceptable. We're not willing to give
up the current behavior, both for backwards-compatibility reasons and
because most of us just plain like it better (ALL UPPER CASE IS UGLY AND
HARDER TO READ...). So we'd need to support both, and that's hard.
Easy answers like "make it a configuration option" don't work because
they break too much stuff, including a whole lot of client-side code
that we don't control.

There are a couple of long threads in the pghackers archives discussing
pros and cons of different possibilities, if you're interested.

regards, tom lane