| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: SELECT problem |
| Date: | 2002-06-23 17:08:37 |
| Message-ID: | 3D160095.4080405@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> If the original report is correct then SQL Server matches names
> case-insensitively (at least when they're not quoted), which seems
> a much larger departure from the spec behavior to me. For example,
> I'd think they'd have to reject table definitions that contain
> columns named both "foo" and "FOO", else they'd have
> effectively-duplicate column names. Can anyone verify their behavior?
>
MSSQL Server lets you choose *on installation* whether you want
case-sensitive or case-insensitive behavior (at least through MSSQL 7,
not sure about MSSQL 2000). If you pick the latter, both identifiers and
data are case-insensitive. Even with MSSQL Server, if a case-sensitive
install is picked, I believe it would break this app. (which is clearly
flawed anyway).
JOe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-06-23 17:21:42 | Re: Optimizing suggestions |
| Previous Message | David Ford | 2002-06-23 16:57:59 | Re: Optimizing suggestions |