Re: Continuing encoding fun....

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Marc Herbert" <Marc(dot)Herbert(at)continuent(dot)com>, <pgsql-odbc(at)postgresql(dot)org>
Cc: <unixodbc-dev(at)unixodbc(dot)org>
Subject: Re: Continuing encoding fun....
Date: 2005-11-24 15:23:22
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E31D@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Marc Herbert
> Sent: 24 November 2005 14:18
> To: pgsql-odbc(at)postgresql(dot)org
> Cc: unixodbc-dev(at)unixodbc(dot)org
> 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

Browse pgsql-odbc by date

  From Date Subject
Next Message lothar.behrens 2005-11-24 17:04:20 Delete row (SQLSetPos) and then fetch over ?
Previous Message noreply 2005-11-24 14:25:40 [ psqlodbc-Bugs-1000417 ] odbc_lib_connect() returns "Specified driver could not be loaded due to system error 182 (PostgreSQL ANSI)"