Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 1AE3A9FB1C2; Thu, 2 Nov 2006 06:28:12 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 37316-01; Thu, 2 Nov 2006 10:28:08 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 7D3EB9FB1BA; Thu, 2 Nov 2006 06:28:08 -0400 (AST) thread-index: Acb+aZcliFQCpUaeQImSR4aA5lcpAg== Received: from [192.168.0.31] ([82.133.64.220]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Nov 2006 05:28:07 -0500 Subject: Re: [HACKERS] Case Preservation disregarding case Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 From: "Simon Riggs" To: "Chuck McDevitt" Cc: "Tom Lane" , "Stephan Szabo" , "beau hargis" , , In-Reply-To: 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> Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 02 Nov 2006 10:27:44 +0000 Message-ID: <1162463264.3587.281.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 02 Nov 2006 10:28:08.0078 (UTC) FILETIME=[96BF52E0:01C6FE69] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/65 X-Sequence-Number: 26717 On Wed, 2006-11-01 at 11:31 -0500, Chuck McDevitt wrote: > But, stepping back from all that, what is it the users want? > > 1) When re-creating a CREATE TABLE statement from whatever catalog > info, they'd like the names to come back exactly as then entered them. > If I do: > CREATE TABLE BobsTable (WeeklySales numeric(10,2), > "SomeStrangeName" int); > > They'd like to see exactly that when the CREATE TABLE gets > re-created, not what we do now: > > CREATE TABLE bobstable (weeklysales numeric(10,2), > "SomeStrangeName" int); This would be very good indEEd. It can be very annoying trying to locate a table when the user swears they called it one thing and actually the case or quotation is different. Current behaviour isn't useful, even if it is "onspec" (or is that OnSpec?). Would be better to make this behaviour a userset switchable between the exactly compliant and the more intuitive. 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. It's certainly an error of best practice, even if its not actually a bug. > 2) When doing reports, they'd like the name as entered to be the title > of the column: > Select * from bobstable; > > Would be nice if they saw this: > WeeklySales SomeStrangeName > ----------- --------------- ... > Producing "?column?" or somesuch to use in the report, it could return a > title like "sum(WeeklySales)" That would be just great. I'm not sure the spec says what the titles should be, does it? -- Simon Riggs EnterpriseDB http://www.enterprisedb.com