| From: | "Chuck McDevitt" <cmcdevitt(at)greenplum(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "beau hargis" <beauh(at)bluefrogmobile(dot)com>, pgsql-sql(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Case Preservation disregarding case |
| Date: | 2006-10-31 17:13:31 |
| Message-ID: | EB48EBF3B239E948AC1E3F3780CF8F88012F89FA@MI8NYCMAIL02.Mi8.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
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(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, October 30, 2006 10:35 PM
To: Chuck McDevitt
Cc: beau hargis; pgsql-sql(at)postgresql(dot)org; pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] [SQL] Case Preservation disregarding case
sensitivity?
"Chuck McDevitt" <cmcdevitt(at)greenplum(dot)com> writes:
> At Teradata, we certainly interpreted the spec to allow
case-preserving,
> but case-insensitive, identifiers.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-10-31 17:27:27 | Re: --single-transaction doc clarification |
| Previous Message | Chuck McDevitt | 2006-10-31 17:11:16 | Re: [HACKERS] Case Preservation disregarding case |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Curtis Scheer | 2006-10-31 17:15:26 | Table Relationships |
| Previous Message | Chuck McDevitt | 2006-10-31 17:11:16 | Re: [HACKERS] Case Preservation disregarding case |