Jim -

I would like to 'second' the ideas already presented. I think that the ODBC driver should move forward and support double quotes as identifiers and single quotes as literals.

The only way that I could see having an attribute for the driver would be to handle the quote situtation according to SQL as the default. It would make the driver easier to integrate and use with the applications already making use of drivers from other vendors whose products do differentiate between the quotes.


Just my thoughts
-Mark


IB-Architect@egroups.com wrote:

> InterBase SQL, now old enough to drive in 45 states, originally

supported both single and double quoted literal strings. The
current SQL standard provides for single quoted literal strings
and double quoted identifier strings. This is pain, but has
to be dealt with.

V6 InterBase differentiates between the two by a "sql dialect"
identifier passed in on the isc_dsql_prepare and isc_execute_immediate
calls.

The question of the hour is how the ODBC driver should interprete
SQL strings since a) existing programs use double quotes for
literals and b) new program will use double quotes for identifiers.

There isn't a good way to handle this because in a good world this
wouldn't happen. Please note that BLR was immune to this sort
of problem [sigh].

A candidate solution would be to an attribute to the driver
connect string passed through SQLDriverConnect. It would also
be configurable through the ODBC configuration mechanism,
so a system default could be established.

Does anybody have any better ideas?

Jim Starkey

------------------------------------------------------------------------
Click here for savings: beMANY!
http://click.egroups.com/1/4115/4/_/830676/_/959111443/
------------------------------------------------------------------------

To unsubscribe from this group, send an email to:
IB-Architect-unsubscribe@onelist.com