Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id EF1639FA6B5; Tue, 14 Nov 2006 14:44:13 -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 30735-03; Tue, 14 Nov 2006 18:44:08 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 87B7E9FB232; Tue, 14 Nov 2006 14:44:07 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id kAEIhwv04665; Tue, 14 Nov 2006 13:43:58 -0500 (EST) From: Bruce Momjian Message-Id: <200611141843.kAEIhwv04665@momjian.us> Subject: Re: Case Preservation disregarding case sensitivity? In-Reply-To: <200610301928.51255.beauh@bluefrogmobile.com> To: beau hargis Date: Tue, 14 Nov 2006 13:43:58 -0500 (EST) CC: pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/150 X-Sequence-Number: 26802 beau hargis wrote: > Having installed DB2 Enterprise today and taking it for a spin, it does indeed > behave in a similar manner. However, after reading through both > specifications, it seems that DB2 follows more of the spec than PostgreSQL. > The specifications state that for purpose of comparing identifiers, both > shall be converted to upper-case. DB2 displays all identifiers in upper-case > whereas PostgreSQL displays all identifiers in lower-case. This alone would > be a deviation from the specification. True. We lowercase because historically we have, and because all-upper-case is hard to read. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +