In continuation to my previous mail, here is an overview on the approach
that we have taken. We had a few design goals when we started on this
1. ODBC driver should still support socket mode.
2. Use if-defs minimally.
3. The code change should be minimal.
4. Use a compile time flag USE_LIBPQ to switch between libPQ and socket.
During connection, we are including the pgconn into the ConnectionClass
instead of SocketClass. This part is already done.
For the resultSet, we are mapping pgresult to QResultClass in
CC_send_query. All the data returned will be added to manual_tuples in
QResultClass and the manual_result will be set to true in
We are hoping there should be no more changes since only QResultClass is
used in other places.
We hope to be done on this by end of this week and will submit a patch
early next week.
From: Sivakumar K
Sent: Tuesday, June 07, 2005 11:21 AM
To: 'pgman(at)candle(dot)pha(dot)pa(dot)us'; 'fuerth(at)sqlpower(dot)ca'
Cc: 'jd(at)commandprompt(dot)com'; 'pgsql-odbc(at)postgresql(dot)org'
Subject: RE: [ODBC] Frontend/Backend protocol 3.0
We, at Pervasive, are working in making the ODBC driver use the libPQ
while retaining the socket connection too (using a compile time flag).
are planning to provide a lump-sum update on this task since it does not
make sense for incremental updates. We are also doing bug-fixing and
open bugs (where we can) in the drivers which are provided as
updates. I will post an email on approach shortly.
[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Bruce Momjian
Sent: Tuesday, June 07, 2005 5:05 AM
To: Jonathan Fuerth
Cc: Joshua D. Drake; pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] Frontend/Backend protocol 3.0
Jonathan Fuerth wrote:
> On Jun 6, 2005, at 5:39 PM, Joshua D. Drake wrote:
> >>> I don't think I'm the only person who has been suffering from a
> >>> of background knowledge in this regard.
> >> OK, who is working on improving ODBC at this point? Please give us
> >> status report.
> > My understanding is that there are two ODBC Projects.
> > 1. ODBCng which is the GPL Command Prompt venture
> This seems clear enough--a from-scratch, GPL/commercial licensed ODBC
> driver which doesn't use libpq and only works with PostgreSQL backend
> >=8.0. Command Prompt will host this separately from the existing
> psqlodbc project.
> > 2. ODBC which is the original LGPL version and is being worked on by
> > Pervasive.
> I'm fuzzy on this one. Is pervasive just contributing incremental
> updates to the existing driver in the existing CVS repository, or will
> they post a lump-sum update to the driver one day, or will they fork
> the project and host their version on their own site?
> I can't find any evidence that they've publicly forked the project (or
> made any improvements to the odbc driver), but that doesn't mean they
> haven't been working on something in secret.
> Thanks for helping me discover these other projects. Now that we can
> get SQLSTATE from the backend, the driver works with our product
> is not open source).
> The next step will be to optimise SQL INSERT and UPDATE performance,
> and the most obvious place to start is with the new bind/execute part
> of the v3 backend protocol. I'm trying to decide if it's worth
> implementing on top of our current patched driver, or if I should just
> wait for Pervasive or Command Prompt to do it.
I am fuzzy on what Pervasive is doing and hope they will jump into this
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
pgsql-odbc by date
|Next:||From: Dave Page||Date: 2005-06-07 09:31:22|
|Subject: Re: Frontend/Backend protocol 3.0|
|Previous:||From: selvaraj balasundaram||Date: 2005-06-07 07:33:58|
|Subject: Problem while using Refcursors in Postgres with .NET|