Re: Continuing encoding fun.... - Mailing list pgsql-odbc

From Johann Zuschlag
Subject Re: Continuing encoding fun....
Date
Msg-id 431C127B.7080907@online.de
Whole thread Raw
In response to Continuing encoding fun....  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgsql-odbc
Dave Page schrieb:

>
>
>
>
>>-----Original Message-----
>>From: pgsql-odbc-owner@postgresql.org
>>[mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Dave Page
>>Sent: 03 September 2005 20:48
>>To: pgsql-odbc@postgresql.org
>>Cc: Hiroshi Saito; Marko Ristola; Johann Zuschlag
>>Subject: [ODBC] Continuing encoding fun....
>>
>>Therefore, it seems to me that the only thing to do is to
>>reinstate the
>>#ifdef UNICODE preprocessor definitions in the source code (that I now
>>with I hadn't removed!), and ship 2 versions of the driver - a Unicode
>>one, and an ANSI/Multibyte version (ie. What 07.xx was).
>>
>>
>
>Attached is a patch to do this (apologies for the size, it seems that
>options.c had broken line ends).
>
>With this patch, you can build either the old style ANSI/Multibyte
>driver, or the Unicode driver. I've also removed the -libpq suffix that
>was added for testing, as this patch gives the driver a new name anyway.
>When installed on a Windows system, you then get:
>
>psqlodbca.dll "PostgreSQL ANSI"
>psqlodbcw.dll "PostgreSQL Unicode"
>
>Unless anyone has a better solution, I think this is the best fix to
>allow users with non-Unicode friendly apps to work as they used to with
>the older driver.
>
>Please shout ASAP if you object!!
>
>Regards, Dave
>
>
It is ok for me.

Can you send me the dll for the ANSI Driver?

It is not possible to just put a switch in the driver menu?

Regards,
Johann


pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Continuing encoding fun....
Next
From: "Dave Page"
Date:
Subject: Re: Continuing encoding fun....