Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 7A9199FB3AD;
	Tue, 31 Oct 2006 14:22:48 -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 58372-01; Tue, 31 Oct 2006 14:22:42 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210])
	by postgresql.org (Postfix) with ESMTP id AC2D09FB3AC;
	Tue, 31 Oct 2006 14:22:41 -0400 (AST)
Received: by megazone.bigpanda.com (Postfix, from userid 1001)
	id A283635095; Tue, 31 Oct 2006 10:22:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by megazone.bigpanda.com (Postfix) with ESMTP
	id A05823506C; Tue, 31 Oct 2006 10:22:40 -0800 (PST)
Date: Tue, 31 Oct 2006 10:22:40 -0800 (PST)
From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Chuck McDevitt <cmcdevitt@greenplum.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
	beau hargis <beauh@bluefrogmobile.com>, pgsql-sql@postgresql.org,
	pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Case Preservation disregarding case
In-Reply-To: <EB48EBF3B239E948AC1E3F3780CF8F88012F89F8@MI8NYCMAIL02.Mi8.com>
Message-ID: <20061031101314.R83230@megazone.bigpanda.com>
References: <200610271623.37525.beauh@bluefrogmobile.com>
	<1162003132.687.8.camel@pampa>
	<200610301928.51255.beauh@bluefrogmobile.com>
	<23177.1162265010@sss.pgh.pa.us>
	<EB48EBF3B239E948AC1E3F3780CF8F88012F88DD@MI8NYCMAIL02.Mi8.com>
	<24861.1162276496@sss.pgh.pa.us>
	<EB48EBF3B239E948AC1E3F3780CF8F88012F89F8@MI8NYCMAIL02.Mi8.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200610/248
X-Sequence-Number: 26637

On Tue, 31 Oct 2006, Chuck McDevitt wrote:

> We treated quoted identifiers as case-specific, as the spec requires.
>
> In the catalog, we stored TWO columns... The column name with case
> converted as appropriate (as PostgreSQL already does), used for looking
> up the attribute,
> And a second column, which was the column name with the case exactly as
> entered by the user.

Wouldn't using that second column's value tend to often violate 5.2SR10
(at least that's the reference item in SQL92)? AFAICT, that rule basically
says that the regular identifier is equivalent to the case-folded one for
purposes of information and definition schema and similar purposes which
seems like it would be intended to include things like column labeling for
output. There's a little bit of flexibility there on both similar purposes
and equivalence, though.

----

10) The <identifier body> of a <regular identifier> is equivalent
    to an <identifier body> in which every letter that is a lower-
    case letter is replaced by the equivalent upper-case letter
    or letters. This treatment includes determination of equiva-
    lence, representation in the Information and Definition Schemas,
    representation in the diagnostics area, and similar uses.