From: Chuck McDevitt <cmcdevitt@greenplum.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: beau hargis <beauh@bluefrogmobile.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Case Preservation disregarding case
Date: Tue, 31 Oct 2006 12:13:31 -0500
Message-ID: <EB48EBF3B239E948AC1E3F3780CF8F88012F89FA@MI8NYCMAIL02.Mi8.com> (raw)
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>
Oh... And Microsoft SQLServer does something similar.
At Greenplum, we've already gotten complaints from customers about this
when they were switching from MSSQL to GP's PostgreSQL-based database.
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Monday, October 30, 2006 10:35 PM
To: Chuck McDevitt
Cc: beau hargis; pgsql-sql@postgresql.org; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] [SQL] Case Preservation disregarding case
sensitivity?
"Chuck McDevitt" <cmcdevitt@greenplum.com> writes:
> At Teradata, we certainly interpreted the spec to allow
case-preserving,
> but case-insensitive, identifiers.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: cmcdevitt@greenplum.com, tgl@sss.pgh.pa.us, beauh@bluefrogmobile.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Case Preservation disregarding case
In-Reply-To: <EB48EBF3B239E948AC1E3F3780CF8F88012F89FA@MI8NYCMAIL02.Mi8.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox