Re: libpq enabled psqlodbc

From: "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>
To: "Jonathan Fuerth" <fuerth(at)sqlpower(dot)ca>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: libpq enabled psqlodbc
Date: 2005-07-01 05:06:59
Message-ID: 02767D4600E59A4487233B23AEF5C5991F1742@blrmail1.aus.pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hi Jonathan,

Thanks!

Currently the plan is to convert the socket code to libpq enabled code,
without any enhancements. We may do the enhancements those you suggested
after finishing all the phases and posting the patch to the community.

Regards

Anoop


-----Original Message-----
From: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Jonathan Fuerth
Sent: Thursday, June 30, 2005 7:55 PM
To: Anoop Kumar
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] libpq enabled psqlodbc

On Jun 30, 2005, at 1:01 AM, Anoop Kumar wrote:

We have completed the first three phases and currently working
on the fourth one. But lot more work needs to be done as the affected
code spans almost the entire odbc code, which needs a thorough checking.
I expect the patch to be submitted in next week.

Anoop, that's great news!

Will this patch enable any of the new protocol features, such as
sqlstate error codes from the backend, rollback to savepoint, and real
prepared statements?

I look forward to this update!

-Jonathan

Browse pgsql-odbc by date

  From Date Subject
Next Message Joel Fradkin 2005-07-01 12:44:44 What to do about errors returned by odbc
Previous Message Zoltan Boszormenyi 2005-07-01 04:23:19 Re: libpq enabled psqlodbc