Re: Production version of ODBC drivers

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Mark
> Morgan Lloyd
> Sent: 21 February 2006 10:20
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Production version of ODBC drivers
>
> "Joshua D. Drake" wrote:
>
> > No. There is no fork. There are two FOSS open source drivers:
>
> I'm very sorry, but I think that statement is contradictory:
> the concept ("an
> ODBC client driver for PostgreSQL") forked, even if the code didn't.
>
> Noted that the new driver has been discussed at length in
> this ML before, but
> I'm sure I'm not the only person who's been confused by it
> hence my request for
> clarification.

OK, this is whats happening:

1) Command Prompt (Joshua's company) are writing a new ODBC driver
(ODBCng), which is in very early stages of development. That driver is
not developed here, nor is it the 'official' PostgreSQL driver (though
we are pleased that CP are widening the choices available to users).

2) psqlODBC (the official driver) has changed a bit over time:

- The original driver (ie. <= v08.00.xxxx) implemented it's own comms
layer.

- The 'new' driver (08.01.xxxx) uses libpq instead of it's own comms
layer which means that it uses both the v2 and v3 wire protocols as
appropriate, and adds features such as SSL, Kerberos support, and
.pgpass/pgpass.conf support. This is the driver we recommend you use
(currently 08.01.0200).

- Another driver variant (actually a fork of the code from
07.03.0209ish) is currently being evaluated as a possible replacement
for the current version. It has been enhanced significantly and includes
similar changes to those in 08.01.xxxx, but implemented in a very
different way.

Regards, Dave.