Re: New ODBC driver - Mailing list pgsql-odbc

From Dave Page
Subject Re: New ODBC driver
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4527C0B@ratbert.vale-housing.co.uk
Whole thread Raw
In response to New ODBC driver  (markw@mohawksoft.com)
Responses Re: New ODBC driver
List pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of
> markw@mohawksoft.com
> Sent: 01 December 2004 13:50
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] New ODBC driver
>
> What would be the best way to go about re-writing the ODBC
> driver to use libpq? (I haven't looked at the code in years,
> the last time I looked at it was to find a memory leak.)
>
> Is it possible to do it in stages?
>
> Is the transport sufficiently separated to do a quick change
> to use libpq as the transport, and then gradually use more and more?
>
> My only concern would be that a re-write would re-break a lot
> of functionality.

I haven't looked at it in depth, but I think you will essentially just
need to rewrite connection.c as a libpq wrapper.

I don't think it would be realistic to mix the two approaches though -
if only because they couldn't share a single database connection.

Regards, Dave.

pgsql-odbc by date:

Previous
From: markw@mohawksoft.com
Date:
Subject: New ODBC driver
Next
From: Robert Treat
Date:
Subject: Re: ODBC driver for Windows & future...