Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UuPuV-00044i-0S for pgsql-sql@arkaria.postgresql.org; Wed, 03 Jul 2013 16:28:03 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UuPuU-0003zs-H0 for pgsql-sql@arkaria.postgresql.org; Wed, 03 Jul 2013 16:28:02 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UuPuT-0003zm-QW for pgsql-sql@postgresql.org; Wed, 03 Jul 2013 16:28:01 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UuPuR-0006Eu-Fk for pgsql-sql@postgresql.org; Wed, 03 Jul 2013 16:28:01 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1UuPuO-0002n9-EP; Wed, 03 Jul 2013 12:27:56 -0400 Date: Wed, 3 Jul 2013 12:27:56 -0400 From: Bruce Momjian To: Tom Lane Cc: Dev Kumkar , Thomas Kellerer , pgsql-sql@postgresql.org Subject: Re: Unquoted column names fold to lower case Message-ID: <20130703162756.GC6492@momjian.us> References: <1372858894.60580.YahooMailClassic@web161605.mail.bf1.yahoo.com> <20130703152402.GA6492@momjian.us> <20130703153524.GB6492@momjian.us> <10699.1372868406@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10699.1372868406@sss.pgh.pa.us> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: 0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org On Wed, Jul 3, 2013 at 12:20:06PM -0400, Tom Lane wrote: > Dev Kumkar writes: > > 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. Agreed. I guess we could add it to the "Features We Do Not Want" section of the TODO list, but it rarely comes up. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql