Re: libpq and prepared statements progress for 8.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pg(at)fastcrypt(dot)com, "Greg Stark" <gsstark(at)mit(dot)edu>, "Oliver Jowett" <oliver(at)opencloud(dot)com>, "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: libpq and prepared statements progress for 8.0
Date: 2004-09-17 14:36:41
Message-ID: 21663.1095431801@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
>> From: Dave Cramer [mailto:pg(at)fastcrypt(dot)com]
>> I'd like to know more about the issues you are trying to
>> solve? Seems counter productive for all of us to attempt this
>> independently

> Mainly lack of time :-)

> SSL and v3+ protocol support are the primary issues. If we can use
> libpq, then obviously we don't have to worry about them any more.

Another point is that since the ODBC driver is C anyway, there are no
cross-language issues for it in relying on libpq. This is quite
different IMHO from the situation for JDBC, or DBD::Pg, where there are
advantages in having a single-language solution.

BTW, there is also a pure-Tcl client implementation out there, written
despite the pre-existence of a version sitting atop libpq. Same story:
needing some C code reduces portability, or at least ease of installation.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2004-09-17 15:38:01 R-Tree operators
Previous Message Bruce Momjian 2004-09-17 14:26:18 Re: Others applying patch queue patches