From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Unquoted column names fold to lower case |
Date: | 2013-07-03 21:01:20 |
Message-ID: | CALSLE1P_GVeF12dQJT7LJgdh9cZXYN8p3LN=hPWgWA-NWQXpFQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Thu, Jul 4, 2013 at 1:17 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Quite aside from implementation difficulty, restricting the change to
> just column aliases doesn't make it more palatable. You'd entirely lose
> the argument that the change increases spec compliance, because the spec
> is perfectly clear that a column alias is an identifier just like any
> other. And you'd still be paying a large part of the application
> breakage costs, because the identifiers coming back in query descriptors
> are one of the main ways applications would notice such a change.
True, applications will notice and map only the identifiers coming back in
query descriptor and in cases when the application reading these resultsets
is case-sensitive for descriptors then breakage cost will be there. Hence
was all this discussion to reduce the application breakage cost in
particular cases.
Regards...
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-07-03 23:29:34 | Re: Unquoted column names fold to lower case |
Previous Message | Dev Kumkar | 2013-07-03 20:30:24 | Re: Unquoted column names fold to lower case |