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/
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
