| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <janwieck(at)yahoo(dot)com> |
| Cc: | 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 17:14:38 |
| Message-ID: | 29400.1021050878@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-05-10 17:59:07 | Re: Unbounded (Possibly) Database Size Increase - Test Case |
| Previous Message | Jan Wieck | 2002-05-10 17:05:33 | Re: the parsing of parameters |