Thread: libpq enabled psqlodbc

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


<excerpt><fixed><fontfamily><param>Courier New</param><x-tad-bigger>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.</x-tad-bigger></fontfamily></fixed>


</excerpt>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


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

Anoop Kumar írta:
> We made quite some progress with libpq enabled version of psqlodbc.
>
> Here are the four phases of this:
>
>
>
> Phase 1     Connecting to the database through libpq library
>
> Phase 2     Mapping the Socket ResultSet class with libpq class
>
> Phase 3     Using the libpq mapped classes in all the related areas
>
> Phase 4     Retrieving ResultSet and displaying it to the end user
>
>
>
> 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.
>
>
>
> Regards
>
>
>
> Anoop

Thanks for the great news! May I have some questions, though?
Do your changes make the problems I reported in the past few weeks
go away?

- Complex queries (with OUTER JOIN or subqueries) fetch only
   0 or 1 rows, the following SQLFetch(hStmt) returns error.
- SQLCancel does not work

Best regards,
Zoltán Böszörményi

---

From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Merlin Moncure
Sent: 12 July 2005 13:02
To: Anoop Kumar
Cc: pgsql-odbc@postgresql.org; Joel Fradkin
Subject: Re: [ODBC] libpq enabled psqlodbc

Is it possible to get the current odbc driver patch for review and testing?  Joel is in urgent need of a more stable driver and he might be a good candidate to help test the driver.

 

Merlin

 

---

From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Anoop Kumar
Sent: Thursday, June 30, 2005 1:02 AM
To: pgsql-odbc@postgresql.org
Subject: [ODBC] libpq enabled psqlodbc

 

We made quite some progress with libpq enabled version of psqlodbc.

Here are the four phases of this:

 

Phase 1    Connecting to the database through libpq library

Phase 2    Mapping the Socket ResultSet class with libpq class

Phase 3    Using the libpq mapped classes in all the related areas

Phase 4    Retrieving ResultSet and displaying it to the end user

 

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.

 

Regards

 

Anoop