Re: Continuing encoding fun....
От | Dave Page |
---|---|
Тема | Re: Continuing encoding fun.... |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E31D@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Continuing encoding fun.... ("Dave Page" <dpage@vale-housing.co.uk>) |
Список | pgsql-odbc |
> -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Marc Herbert > Sent: 24 November 2005 14:18 > To: pgsql-odbc@postgresql.org > Cc: unixodbc-dev@unixodbc.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
В списке pgsql-odbc по дате отправления: