Re: Production version of ODBC drivers

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Raymond O'Donnell" <rod(at)iol(dot)ie>, <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Production version of ODBC drivers
Date: 2006-02-21 12:19:48
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40103E294@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Raymond
> O'Donnell
> Sent: 21 February 2006 12:13
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Production version of ODBC drivers
>
> On 21 Feb 2006 at 10:33, Dave Page wrote:
>
> > - 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.
>
> Is this one also libpq-based, or will it retain its own comms layer?

Both actually. It will dynamically load libpq to do things like
Kerberos/SSL, but it will also communicate on the wire itself, allowing
it to do things which aren't so easy through the libpq API.

The code can be seen in the 07_03_ENHANCED branch in CVS. Avoid (or
beware of) the pgfoundry CVs browser though - it gets confused by files
that have been deleted from CVS tip but are still in the branch and
shows them in the attic even though they actually aren't.

Regards, Dave.

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Saito 2006-02-22 10:09:37 Re: Demo version of the 'enhanced' branch
Previous Message Raymond O'Donnell 2006-02-21 12:12:43 Re: Production version of ODBC drivers