Re: libpq and prepared statements progress for 8.0

From: David Wheeler <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Rudy Lippan <rlippan(at)remotelinux(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org, Greg Sabino Mullane <greg(at)turnstep(dot)com>
Subject: Re: libpq and prepared statements progress for 8.0
Date: 2004-09-17 21:08:30
Message-ID: BA3C7C28-08ED-11D9-9CAB-000A95B9602E@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Sep 17, 2004, at 1:54 PM, Tom Lane wrote:

> David Wheeler <david(at)kineticode(dot)com> writes:
>> if I understand a previous post from you, this functionality should be
>> added to libpq, but you haven't had time and aren't sure what the API
>> should look like, anyway, is that correct?
>
> Right. Proposals welcome.

Wish I spoke C! But I don't think it makes sense to support PREPARE in
DBD::Pg without this functionality. :-(

>> Is this the task labeled "allow libpq to check parameterized data
>> types"
>> here?:
>> http://candle.pha.pa.us/cgi-bin/pgopenitems
>
> I think that was something else, but memory is fuzzy.

I'm less sure, since I was the one who asked Jan Wieck about this at
OSCON, for which I believe that this is the relevant discussion:

http://archives.postgresql.org/pgsql-hackers/2004-08/msg00136.php
http://archives.postgresql.org/pgsql-hackers/2004-08/msg00130.php

But maybe Jan and I misunderstood each other?

Regards,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2004-09-17 21:20:06 Default value for stats_command_string (GUC)
Previous Message Tom Lane 2004-09-17 20:54:49 Re: libpq and prepared statements progress for 8.0

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-09-17 21:15:51 Re: oid2name
Previous Message Tom Lane 2004-09-17 20:54:49 Re: libpq and prepared statements progress for 8.0