Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 188039F9EF5; Wed, 15 Nov 2006 13:36:58 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 28626-03; Wed, 15 Nov 2006 13:36:38 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 4E3749F946B; Wed, 15 Nov 2006 13:36:38 -0400 (AST) Received: from [12.174.32.177] (unknown [12.174.32.177]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by noel.decibel.org (Postfix) with ESMTP id 0F59256459; Wed, 15 Nov 2006 11:36:33 -0600 (CST) In-Reply-To: <1163540553.27956.109.camel@silverbirch.site> References: <200610271623.37525.beauh@bluefrogmobile.com> <1162003132.687.8.camel@pampa> <200610301928.51255.beauh@bluefrogmobile.com> <23177.1162265010@sss.pgh.pa.us> <24861.1162276496@sss.pgh.pa.us> <20061031101314.R83230@megazone.bigpanda.com> <14059.1162363105@sss.pgh.pa.us> <1162463264.3587.281.camel@silverbirch.site> <16897.1162482685@sss.pgh.pa.us> <1163540553.27956.109.camel@silverbirch.site> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: "Tom Lane" , "Chuck McDevitt" , "Stephan Szabo" , "beau hargis" , , Content-Transfer-Encoding: 7bit From: Jim Nasby Subject: Re: [HACKERS] Case Preservation disregarding case Date: Wed, 15 Nov 2006 08:47:18 -0700 To: Simon Riggs X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/157 X-Sequence-Number: 26809 On Nov 14, 2006, at 2:42 PM, Simon Riggs wrote: > On Thu, 2006-11-02 at 10:51 -0500, Tom Lane wrote: >> "Simon Riggs" writes: >>> We have namespaces to differentiate between two sources of object >>> names, >>> so anybody who creates a schema where MyColumn is not the same >>> thing as >>> myColumn is not following sensible rules for conceptual distance. >> >> I'd agree that that is not a good design practice, but the fact >> remains >> that they *are* different per spec. >> >>> Would be better to make this behaviour a userset >>> switchable between the exactly compliant and the more intuitive. >> >> That's certainly not happening --- if you make any changes in the >> semantics of equality of type name, it would have to be frozen no >> later than initdb time, for exactly the same reasons we freeze >> locale then (hint: index ordering). > > [Re-read all of this after Bruce's post got me thinking.] > > My summary of the thread, with TODO items noted: > > 1. PostgreSQL doesn't follow the spec, but almost does, with regard to > comparison of unquoted and quoted identifiers. DB2 does this per spec. > > 2. TODO: We could follow the spec, but it would need an initdb option; > some non-SQL:2003 standard PostgreSQL programs would not work as > they do > now. This is considered a minor, low priority item, though. > > 3. TODO: We could set column headers better if we wanted to (rather > than ?column? we could use e.g. Sum_ColumnName etc) Did the idea of preserving the original case and using that for output column names, /d, etc. get shot down? I thought it would be a useful addition... -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)