MIME-Version: 1.0
In-Reply-To: <10699.1372868406@sss.pgh.pa.us>
References: 
 <CALSLE1PeLH4iqEyT5RH=d4Y3VmrRyxm6rvnV9fNC0++u9h-WWw@mail.gmail.com>
 <1372858894.60580.YahooMailClassic@web161605.mail.bf1.yahoo.com>
 <kr1bl9$96d$1@ger.gmane.org> <20130703152402.GA6492@momjian.us>
 <CALSLE1N-WnxujTjD+ED9u4pjFrUnHbm8zr9+SmMvu5NPAMGw1g@mail.gmail.com>
 <20130703153524.GB6492@momjian.us>
 <CALSLE1Pxn7aL1P4tW5vL6GL7h9V1YrZU2KmFeTaHQ2ok4hb_xg@mail.gmail.com>
 <10699.1372868406@sss.pgh.pa.us>
Date: Thu, 4 Jul 2013 00:19:20 +0530
Message-ID: 
 <CALSLE1POR2hJa4HMSNshDoruWsEZ+3miLffnyZLqZ6GmcLTG7Q@mail.gmail.com>
Subject: Re: Unquoted column names fold to lower case
From: Dev Kumkar <devdas.kumkar@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>, Thomas Kellerer <spam_eater@gmx.net>,
 pgsql-sql@postgresql.org
Content-Type: multipart/alternative; boundary=089e01494bb0636e5c04e09febd6
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

--089e01494bb0636e5c04e09febd6
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jul 3, 2013 at 9:50 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> > Any plans to fix this in next release or having a patch to fix this?
>
> No.
>
> This has been discussed (many times) before.  There isn't any feasible
> way to change this behavior without breaking an incredible amount of
> code, much of which isn't even under our control.  The marginal increase
> in standards compliance is not worth the pain --- especially when the
> aspect of the standard in question isn't even one that most of us like.
> (All-upper-case is hard to read.)
>
> If this is a deal-breaker for you, then I'm sorry, but you need to find
> another database.  Postgres settled on this behavior fifteen years ago,
> and we're not changing it now.
>

Again my question was not to change the default behavior and make then
All-upper-case as there is no need to change it.

Rather it was for alias names and if those are with upper case or mix case
then wouldn't it will be good to preserve same. For me these changes to
have aliases quoted are manageable and I was just checking for any thoughts
here.

Regards...

--089e01494bb0636e5c04e09febd6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jul 3, 2013 at 9:50 PM, Tom Lane <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:tgl@sss.pgh.pa.us" target=3D"_blank">tgl@sss.pgh.pa.us</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=3D"im">
&gt; Any plans to fix this in next release or having a patch to fix this?<b=
r>
<br>
</div>No.<br>
<br>
This has been discussed (many times) before. =A0There isn&#39;t any feasibl=
e<br>
way to change this behavior without breaking an incredible amount of<br>
code, much of which isn&#39;t even under our control. =A0The marginal incre=
ase<br>
in standards compliance is not worth the pain --- especially when the<br>
aspect of the standard in question isn&#39;t even one that most of us like.=
<br>
(All-upper-case is hard to read.)<br>
<br>
If this is a deal-breaker for you, then I&#39;m sorry, but you need to find=
<br>
another database. =A0Postgres settled on this behavior fifteen years ago,<b=
r>
and we&#39;re not changing it now.<br></blockquote><div><br>Again my questi=
on was not to change the default behavior and make then All-upper-case as t=
here is no need to change it. <br><br>Rather it was for alias names and if =
those are with upper case or mix case then wouldn&#39;t it will be good to =
preserve same. For me these changes to have aliases quoted are manageable a=
nd I was just checking for any thoughts here.<br>
<br></div><div>Regards...<br></div></div></div></div>

--089e01494bb0636e5c04e09febd6--