| From: | "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> |
|---|---|
| To: | kleptog(at)svana(dot)org |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Returning multiple result sets |
| Date: | 2005-11-20 20:06:10 |
| Message-ID: | BAY20-F2A7AE6DE50CE73B2C6FB8F9500@phx.gbl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello
I thinking about solution based on setof cursors. This solustion has three
big minus:
1. I can "unpack" cursors after finish of called procedure. If I get
exception, or long query, I can show nothing.
2. Old clients don't understand and don't unpack cursor. Statement call is
(+/-) == statement SELECT (more if call return only one table).
3. twice communication.
backend client
==============
<--------------------- call
-----------------------> cursors
<---------------------- select cursor
------------------------> table
this isn't pretty solution. May be with minimal changes in code. I think,
this need bigger changes and support next class of stored objects.
best regards
Pavel Stehule
_________________________________________________________________
Emotikony a pozadi programu MSN Messenger ozivi vasi konverzaci.
http://messenger.msn.cz/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-11-20 20:30:15 | Re: Numeric 508 datatype |
| Previous Message | Martijn van Oosterhout | 2005-11-20 18:18:18 | Re: Returning multiple result sets |