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
