Subject | Re: [Firebird-Architect] RFC: Please unify stored procedure execution |
---|---|
Author | Nando Dessena |
Post date | 2004-12-21T10:00:57Z |
Martijn,
M> EXECutable procedures can have output parameters just fine.
...so calling them through select won't hurt. ;-)
M> What we really need ( I agree somewhat with the proposal ) is the
M> server saying, "well, here's a resultset. It's not a SUSPEND inflicted
M> resultset, so there's only 1 row." and "well, here's a resultset. It's a
M> SUSPEND inflicted resultset, so there might be more rows."
Mmm... I don't think so. A mechanism for signaling when a resultset is
finished already exists, the client just has to "fetch until eof".
What Roman is missing (as I understand) is something to help telling
what kind of call syntax to use *beforehand*. As I explained, I think
it would be useful but I don't find it strictly needed as we already
can do without.
Ciao
--
Nando Dessena
http://www.flamerobin.org
M> EXECutable procedures can have output parameters just fine.
...so calling them through select won't hurt. ;-)
M> What we really need ( I agree somewhat with the proposal ) is the
M> server saying, "well, here's a resultset. It's not a SUSPEND inflicted
M> resultset, so there's only 1 row." and "well, here's a resultset. It's a
M> SUSPEND inflicted resultset, so there might be more rows."
Mmm... I don't think so. A mechanism for signaling when a resultset is
finished already exists, the client just has to "fetch until eof".
What Roman is missing (as I understand) is something to help telling
what kind of call syntax to use *beforehand*. As I explained, I think
it would be useful but I don't find it strictly needed as we already
can do without.
Ciao
--
Nando Dessena
http://www.flamerobin.org