Re: New ODBC driver - Mailing list pgsql-odbc

From markw@mohawksoft.com
Subject Re: New ODBC driver
Date
Msg-id 16614.24.91.171.78.1101913308.squirrel@mail.mohawksoft.com
Whole thread Raw
In response to Re: New ODBC driver  ("Dave Page" <dpage@vale-housing.co.uk>)
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.

Why is this an issue? Why not create multiple connections?

>
> Regards, Dave.


pgsql-odbc by date:

Previous
From: Robert Treat
Date:
Subject: Re: ODBC driver for Windows & future...
Next
From: Robert Treat
Date:
Subject: Re: ODBC driver for Windows & future...