FreeTDS Development Group

["Thompson, Bill D (London)" <bill_d_thompson AT ml.com>]

Freddy, 

Am I going over old ground to tell you that the SQL server books online says
this (in the section on SET QUOTED_IDENTIFIER)

"The SQL Server ODBC driver and Microsoft OLE DB Provider for SQL Server
automatically set QUOTED_IDENTIFIER to ON when connecting. 
This can be configured in ODBC data sources, in ODBC connection attributes,
or OLE DB connection properties. 
SET QUOTED_IDENTIFIER defaults to OFF for connections from DB-Library
applications."

Bill


> -----Original Message-----
> From: ZIGLIO Frediano [SMTP:Frediano.Ziglio AT vodafone.com]
> Sent: 05 December 2003 15:50
> To:   freetds AT lists.ibiblio.org
> Subject:      [freetds] OpenOffice problems - quote or not quote ? (was
> "Error in SQLGetInfo for SQL_FILE_USAGE")
> 
> Should ODBC enable QUOTED_IDENTIFIER? What character should ODBC return
> from SQLGetInfo(SQL_IDENTIFIER_QUOTE_CHAR)?
> 
> I did some tests yestarday with Sybase server. 
> 
> create table test (i int)
> Ok
> select * from "test"
> Error
> set quoted_identifier on
> Ok
> select * from "test"
> Ok
> select * from "tempdb"."dbo"."test"
> Error ??
> select * from tempdb."dbo"."test"
> Ok ??
> create table "a!@()*&" (i int)
> Ok
> 
> Well... still same questions... The correct options seems two
> 1- enable QUOTED_IDENTIFIER (ON) and return "\"" as separator. This is
> SQL92 compliant (and mssql too). However we have to remove quotation
> from db name (or, using other words we have to remove quoting when
> unneeded). So clients can use even strange names for tables/fields...
> 2- do not enable QUOTED_IDENTIFIER (OFF) and return "" (an empty string)
> as separator.
> 
> 2 is faster to implement but IMHO 1 is better. Perhaps 2 for 0.62 and 1
> for 0.63 ... ?
> 
> freddy77
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds