Subject | Re: [Firebird-Architect] RFC: Please unify stored procedure execution |
---|---|
Author | Fabricio Araujo |
Post date | 2004-12-24T04:11:49Z |
I'm adept of the KIS principle: Keep It Simple.
Subtle rules only make your life worse. So, my
the ideal solution (IMHO) is: EXECUTE only
execute. No result set. SELECT retrieves
result set (0..n rows) -- only if the proc have output parms
otherwise throws a exception. The end of the
procedure is treated as a SUSPEND keyword
and the result set is one row -- if there are a
FOR SELECT .. DO loop, it will return only the
last state of return vars.
No need to:
1) Parse blr
2) Parse code
3) *put here any other "clever" way to guess what type of proc you are
using*
So, with this settled, the only step to recognize a
SELEC proc is verifying if it have return parms.
<rant> This subject comes back and forth from time
to time... At least since 1998 (the time when I began
lurking in IB lists).</rant>
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.4 - Release Date: 22/12/2004
Subtle rules only make your life worse. So, my
the ideal solution (IMHO) is: EXECUTE only
execute. No result set. SELECT retrieves
result set (0..n rows) -- only if the proc have output parms
otherwise throws a exception. The end of the
procedure is treated as a SUSPEND keyword
and the result set is one row -- if there are a
FOR SELECT .. DO loop, it will return only the
last state of return vars.
No need to:
1) Parse blr
2) Parse code
3) *put here any other "clever" way to guess what type of proc you are
using*
So, with this settled, the only step to recognize a
SELEC proc is verifying if it have return parms.
<rant> This subject comes back and forth from time
to time... At least since 1998 (the time when I began
lurking in IB lists).</rant>
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.4 - Release Date: 22/12/2004