| From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jan Wieck <janwieck(at)yahoo(dot)com>, Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: the parsing of parameters |
| Date: | 2002-05-10 18:25:14 |
| Message-ID: | 200205101825.g4AIPEL02016@saturn.janwieck.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Jan Wieck <janwieck(at)yahoo(dot)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(at)Yahoo(dot)com #
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-05-10 18:40:36 | Re: troubleshooting pointers |
| Previous Message | large scale | 2002-05-10 18:04:17 | Join of small table with large table |