logo       
Google Custom Search
    AddThis Social Bookmark Button

Re: Continuing encoding fun....: msg#00206

Subject: Re: Continuing encoding fun....
 

> -----Original Message-----
> From: pgsql-odbc-owner@xxxxxxxxxxxxxx 
> [mailto:pgsql-odbc-owner@xxxxxxxxxxxxxx] On Behalf Of Marc Herbert
> Sent: 24 November 2005 14:18
> To: pgsql-odbc@xxxxxxxxxxxxxx
> Cc: unixodbc-dev@xxxxxxxxxxxx
> Subject: Re: [ODBC] Continuing encoding fun....
> 
> > If Microsoft intended the DM to do the conversion when they 
> wrote the
> > spec, why would they then add the same functionality to 
> their driver?
> 
> 
> Here is a hypothesis: the checkbox in SQL Server driver is actually a
> switch between the ANSI version and the Unicode version of this
> driver.  That would be pretty much consistent with all the above. The
> only inconsistency would be: "The driver converts...", to be actually
> read as: "This setting triggers the conversion operated by the DM".
> 
> What do you think?

The DM detects whether the driver is Unicode or not from the presence of
the SQLConnectW function
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/h
tm/odbcunicode_drivers.asp). Whether or not this is exported is
determined at compile time and cannot be changed at runtime.

Regards, Dave

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend




Try Searching:
servers, voip, java, networking, microsoft ...
<Prev in Thread] Current Thread [Next in Thread>