> -----Original Message-----
> From: Hiroshi Inoue [mailto:inoue@tpf.co.jp]
> Sent: 28 August 2006 02:00
> To: Dave Page
> Cc: Hiroshi Saito; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] [COMMITTERS] psqlodbc - psqlodbc: Fixed
> dllname of win32 ANSI: psqlodbca Unicode:
>
> I'm not sticking to the official ANSI version so much.
> Though I don't remember well, probably I didn't add
> psqlodbca.def to CVS intentionally when I added the
> ANSI_VERSION option to win32.mak.
> My hope is to leave the ANSI_VERSION option of win32.mak
> as it is even though it is not supported officially.
> Because it's very troublesome to maintain separate makefiles
> for other settings, I removed duplicates from win32.mak
> as much as possible and integrated the offical Unicode
> version and my local ANSI version.
> I've provided the ANSI version in my site for the people who
> are unhappy with the Unicode version though I've rarely
> tested it by myself and not updated it so often. Though I'm
> not sure if I would continue the ANSI version in the future,
> I hope I would be able to test the ANSI vesrion easily by
> myself.
OK. At the moment, the installer is setup to install the Unicode driver
as 'PostgreSQL'. As this is something we cannot keep chopping and
changing, and we're about to set things in stone for 8.2 - should I make
that 'PostgreSQL Unicode'? Should we include the ANSI driver as well for
now, or just ship the Unicode?
Although I'd like to have only the one driver, if there are real
problems with those remaining latin/BDE issues I'm happy to go with 2 -
we just can't keep changing the driver name in production releases!!
> There's another new option MSDTC in win32.mak. Is it OK that
> the option is ON by default ?
I don't see any problem with new features as long as they are stable and
don't break backwards compatibility. MSDTC support sounds like a fine
improvement.
Regards, Dave.