From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Jonathan Gardner <jgardner(at)jonathangardner(dot)net>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Open items |
Date: | 2004-08-03 18:46:37 |
Message-ID: | 2600.1091558797@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> Having done something similar for the SPI manager once, so that
> parameters can have unknown type and the code calling SPI_prepare() will
> find the chosen types in the type array, so that the code calling
> SPI_execp() can do the appropriate type casting, my idea is that
> preparing a statement does the same and exec prepared actually accepts
> unknown type arguments and calls the typein function before running the
> plan. However, I still need to look at the code ...
This is already *done*. All we need is to devise a reasonable API for
libpq to provide access to the V3-protocol Prepare message. I suspect
that we'd want it to bundle a Prepare and a Describe Statement
operation, so that the user would get back the list of actual argument
types in the same call that issues the prepare. But I haven't thought
it through in detail.
> If this is doable that way, we could log it as an open issue that needs
> to be finished for release.
[ shrug ] Arguably it was something that should have been done for 7.4.
If someone wants to step up to the plate now, I won't stand in the way.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-03 18:55:20 | Re: Anybody have an Oracle PL/SQL reference at hand? |
Previous Message | Peter Eisentraut | 2004-08-03 17:33:40 | Re: pgxs: build infrastructure for extensions v4 |