Subject | Re[2]: [Firebird-Architect] RFC: Please unify stored procedure execution |
---|---|
Author | Dmitry Kuzmenko |
Post date | 2004-12-21T10:34:11Z |
Hello, Martijn!
Tuesday, December 21, 2004, 12:50:06 PM, you wrote:
MT> What we really need ( I agree somewhat with the proposal ) is the
MT> server saying, "well, here's a resultset. It's not a SUSPEND inflicted
MT> resultset, so there's only 1 row." and "well, here's a resultset. It's a
MT> SUSPEND inflicted resultset, so there might be more rows."
I don't understand, who are "we" who need this. :-)
SQL command can return result of it execution (ok or error), return 1
row or return many rows. Procedure with suspend can return 1 row too.
I don't see any criminal if programmer sometimes say - oops! I forgot
to add suspend to my procedure that I used in select statement.
p.s. I don't care how execure procedure call in IBStoredProc works,
but seems that here is no "resultset".
--
Dmitri Kouzmenko
Tuesday, December 21, 2004, 12:50:06 PM, you wrote:
MT> What we really need ( I agree somewhat with the proposal ) is the
MT> server saying, "well, here's a resultset. It's not a SUSPEND inflicted
MT> resultset, so there's only 1 row." and "well, here's a resultset. It's a
MT> SUSPEND inflicted resultset, so there might be more rows."
I don't understand, who are "we" who need this. :-)
SQL command can return result of it execution (ok or error), return 1
row or return many rows. Procedure with suspend can return 1 row too.
I don't see any criminal if programmer sometimes say - oops! I forgot
to add suspend to my procedure that I used in select statement.
p.s. I don't care how execure procedure call in IBStoredProc works,
but seems that here is no "resultset".
--
Dmitri Kouzmenko