Re: [COMMITTERS] psqlodbc - psqlodbc: Fixed dllname of win32 ANSI: psqlodbca Unicode: - Mailing list pgsql-odbc

From Dave Page
Subject Re: [COMMITTERS] psqlodbc - psqlodbc: Fixed dllname of win32 ANSI: psqlodbca Unicode:
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E40154C84C@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Re: [COMMITTERS] psqlodbc - psqlodbc: Fixed dllname of win32 ANSI: psqlodbca Unicode:  ("Hiroshi Saito" <z-saito@guitar.ocn.ne.jp>)
List pgsql-odbc

> -----Original Message-----
> From: Hiroshi Saito [mailto:z-saito@guitar.ocn.ne.jp]
> Sent: 25 August 2006 09:17
> To: Dave Page; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] [COMMITTERS] psqlodbc - psqlodbc: Fixed
> dllname of win32 ANSI: psqlodbca Unicode:
>
> > What is this change for Hiroshi? We deprecated the ANSI
> driver because
> > the correctly functioning Unicode driver will handle ascii data just
> > fine. We don't want it back again.
>
> Ah, The user of the Latin character-set had dissatisfaction
> in UNICODE.
> And Inoue-san considered carefully and he judged that ANSI
> was still required.
> Then, it was able to help the problem. I think It is a
> mission to help the user uses.

That is a major change that wasn't discussed on the mailing lists that
I'm aware of. Why is ANSI still required? No other DBMS that I'm aware
of has to have 2 drivers. Why can't the actual problem be fixed?

Changing back to 2 drivers again is a major pain because it means
renaming all the DLLs and drivers yet again - something that has the
potential to *really* annoy users.

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: [COMMITTERS] psqlodbc - psqlodbc: Fixed dllname of win32 ANSI: psqlodbca Unicode:
Next
From: "Ezequias Rodrigues da Rocha"
Date:
Subject: Problem with VPN