From: | David Wheeler <david(at)kineticode(dot)com> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Rudy Lippan <rlippan(at)remotelinux(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: libpq and prepared statements progress for 8.0 |
Date: | 2004-09-18 20:22:50 |
Message-ID: | 8347888D-09B0-11D9-BC11-000A95B9602E@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Sep 18, 2004, at 1:09 PM, Oliver Jowett wrote:
> Well, obviously. I haven't modified the backend code to accept
> 'unknown' in PREPARE..
Right, and that's what we're looking for.
> My point was the client does *not* need to know the type inferred by
> the PREPARE in the 'unknown' case to make use of the resulting
> statement. It can pass all parameters as text and use the type
> inference that happens on EXECUTE -- as is happening in the EXECUTE
> quoted above.
Yes, that's fine, but it's PREPARE that's at issue here, not EXECUTE.
Regards,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2004-09-18 20:28:54 | Re: libpq and prepared statements progress for 8.0 |
Previous Message | Jeroen T. Vermeulen | 2004-09-18 20:13:29 | Re: transaction idle timeout in 7.4.5 and 8.0.0beta2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2004-09-18 20:28:54 | Re: libpq and prepared statements progress for 8.0 |
Previous Message | Oliver Jowett | 2004-09-18 20:09:35 | Re: libpq and prepared statements progress for 8.0 |