Jan Wieck wrote:
> Tom Lane wrote:
> > Jan Wieck <[EMAIL PROTECTED]> writes:
> > >> Hmm. So your vision of PREPARE would allow the backend to reply
> > >> with a list of parameter types. How would you envision that working
> > >> exactly?
> >
> > > I guess there's some sort of statement identifier you use to
> > > refer to something you've prepared. Wouldn't a function call
> > > returning a list of names or type oid's be sufficient?
> >
> > I was thinking of having the type names returned unconditionally,
> > perhaps like a SELECT result (compare the new behavior of EXPLAIN).
> > But if we assume that this won't be a commonly used feature, maybe
> > a separate inquiry operation is better.
>
> I wouldn't mind. One way or the other is okay with me.
>
> Reminds me though of another feature we should have on the
> TODO. INSERT/UPDATE/DELETE ... RETURNING ...
TODO already has:
o Allow INSERT/UPDATE ... RETURNING new.col or old.col; handle
RULE cases (Philip)
Do we need DELETE too?
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
