On Thu, Feb 20, 2003 at 02:36:04PM -0800, Jeff Zucker wrote:
Jeff Zucker wrote:
There is no database independent way to match a delimited identifier
to an undelimited identifier.
That part of my previous post is correct, but my examples were bad.
Here is a better explanation with
Tim Bunce wrote:
In ODBC, a delimited identifier is equal to an undelimited identifiers
if it matches *case-insenitively*.
By ODBC I presume you mean windows ODBC using windows database like
Access or MSSQL, because on windows case-insenitivity is the norm.
Yes, correct, I checked against the
Francois Desarmenien wrote:
On Thu, 20 Feb 2003 14:44:02 -0500
Jose Blanco [EMAIL PROTECTED] wrote:
Any ideas why SQL statements like this one:
SELECT collid FROM Collection where collid= '123' and (userid = 'JoseA' or
userid = 'JoseB')
Are not working with SQL::Statement version 1.005, but
On Thu, 20 Feb 2003, Jeff Zucker wrote:
Francois Desarmenien wrote:
On Thu, 20 Feb 2003 14:44:02 -0500
Jose Blanco [EMAIL PROTECTED] wrote:
Any ideas why SQL statements like this one:
SELECT collid FROM Collection where collid= '123' and (userid = 'JoseA' or
userid = 'JoseB')
Are
Rudy Lippan wrote:
I am confused. IIRC, SQL-99 (I don't have a 92 ref) says that delimited
identifiers are case sensitive so Collection only matches Collection;
however, COLLECTION will match Collection (collection COLLECTION)
because each character of the regular identifier Collection is
Jeff Zucker wrote:
There is no database independent way to match a delimited identifier
to an undelimited identifier.
That part of my previous post is correct, but my examples were bad.
Here is a better explanation with examples from two differing
implementations:
In the ANSI standard, a
