Re: the parsing of parameters - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: the parsing of parameters
Date
Msg-id 200205101825.g4AIPEL02016@saturn.janwieck.net
Whole thread Raw
In response to Re: the parsing of parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: the parsing of parameters  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Jan Wieck <janwieck@yahoo.com> 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 ...


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pgaccess
Next
From: "Ross J. Reedstrom"
Date:
Subject: Re: pgaccess