Firebird Documentation Index → Firebird 2.5 Language Ref. Update → DML statements → EXECUTE BLOCK |
Table of Contents
Find a more recent version at Firebird 5.0 Language Reference: EXECUTE BLOCK
Available in: DSQL
Added in: 2.0
Changed in: 2.1, 2.5
Description: Executes a block of PSQL code as if it were a stored procedure, optionally with input and output parameters and variable declarations. This allows the user to perform “on-the-fly” PSQL within a DSQL context.
Syntax:
EXECUTE BLOCK [(<inparams>
)] [RETURNS (<outparams>
)] AS [<declarations>
] BEGIN [<PSQL statements>
] END<inparams>
::=<param_decl>
= ? [,<inparams>
]<outparams>
::=<param_decl>
[,<outparams>
]<param_decl>
::=paramname
<type>
[NOT NULL] [COLLATEcollation
]<type>
::=sql_datatype
| [TYPE OF]domain
| TYPE OF COLUMNrel
.col
<declarations>
::= See PSQL::DECLARE for the exact syntax
Examples:
This example injects the numbers 0 through 127 and their corresponding ASCII characters into the table ASCIITABLE:
execute block as declare i int = 0; begin while (i < 128) do begin insert into AsciiTable values (:i, ascii_char(:i)); i = i + 1; end end
The next example calculates the geometric mean of two numbers and returns it to the user:
execute block (x double precision = ?, y double precision = ?) returns (gmean double precision) as begin gmean = sqrt(x*y); suspend; endBecause this block has input parameters, it has to be prepared first. Then the parameters can be set and the block executed. It depends on the client software how this must be done and even if it is possible at all – see the notes below.
Our last example takes two integer values,
smallest
andlargest
. For all the numbers in the rangesmallest
..largest
, the block outputs the number itself, its square, its cube and its fourth power.execute block (smallest int = ?, largest int = ?) returns (number int, square bigint, cube bigint, fourth bigint) as begin number = smallest; while (number <= largest) do begin square = number * number; cube = number * square; fourth = number * cube; suspend; number = number + 1; end endAgain, it depends on the client software if and how you can set the parameter values.
Notes:
Some clients, especially those allowing the user to submit several statements at once, may require you to surround the EXECUTE BLOCK statement with SET TERM lines, like this:
set term #; execute block (...) as begin statement1; statement2; end # set term ;#
In Firebird's isql client you must set the terminator
to something other than “;
” before you type in the
EXECUTE BLOCK statement. Otherwise
isql, being line-oriented, will try to execute the part you
have entered as soon as it encounters the first semicolon.
Executing a block without input parameters should be possible with every Firebird client that allows the user to enter his or her own DSQL statements. If there are input parameters, things get trickier: these parameters must get their values after the statement is prepared but before it is executed. This requires special provisions, which not every client application offers. (Firebird's own isql, for one, doesn't.)
The server only accepts question marks (“?
”) as
placeholders for the input values, not “:a
”,
“:MyParam
” etc., or literal values. Client software
may support the “:xxx
” form though, which it will
preprocess before sending it to the server.
If the block has output parameters, you must use SUSPEND or nothing will be returned.
Output is always returned in the form of a result set, just as with a SELECT statement. You can't use RETURNING_VALUES or execute the block INTO some variables, even if there's only one result row.
Changed in: 2.1
Description: Firebird 2.1 and up allow COLLATE clauses in declarations of input/output parameters and local variables.
Example:
execute block (es_1 varchar(20) character set iso8859_1 collate es_es = ?) returns (nl_1 varchar(20) character set iso8859_1 collate du_nl) as declare s_temp varchar(100) character set utf8 collate unicode; begin ... ... end
Changed in: 2.1
Description: Firebird 2.1 and up allow NOT NULL constraints in declarations of input/output parameters and local variables.
Example:
execute block (a int not null = ?, b int not null = ?) returns (product bigint not null, message varchar(20) not null) as declare useless_dummy timestamp not null; begin product = a*b; if (product < 0) then message = 'This is below zero.'; else if (product > 0) then message = 'This is above zero.'; else message = 'This must be zero.'; suspend; end
Changed in: 2.1
Description: Firebird 2.1 and up allow the use of domains instead of SQL data types when declaring input/output parameters and local variables. With the “TYPE OF” modifier only the domain's type is used, not its NOT NULL setting, CHECK constraint and/or default value. If the domain is of a text type, its character set and collation are always included.
Example:
execute block (a my_domain = ?, b type of my_other_domain = ?) returns (p my_third_domain) as declare s_temp type of my_third_domain; begin ... ... end
For input parameters, the collation that comes with the domain is not taken into consideration when comparisons (e.g. equality tests) are made. This is caused by a bug that has been fixed for Firebird 3.
Added in: 2.5
Description: Analogous to the “TYPE OF
domain
” syntax supported since version 2.1, it is now
also possible to declare variables and parameters as having the type of an existing table
or view column. Only the type itself is used; in the case of string types, this includes
the character set and the collation. Constraints and default values are never copied from
the source column.
Example:
create table numbers ( bignum numeric(18), smallnum numeric(9) ) execute block (dividend type of column numbers.bignum = ?, divisor type of column numbers.smallnum = ?) returns (quotient type of column numbers.bignum, remainder type of column numbers.smallnum) as begin quotient = dividend / divisor; remainder = mod (dividend, divisor); suspend; end
For input parameters, the collation that comes with the column's type is not taken into consideration when comparisons (e.g. equality tests) are made. For local variables, the behaviour varies. This is caused by a bug that has been fixed for Firebird 3.
Firebird Documentation Index → Firebird 2.5 Language Ref. Update → DML statements → EXECUTE BLOCK |