Helen,

> If you are seeing this in Firebird (where it is supposed to
> have been fixed
> so that the engine re-initialises the variables) then we
> certainly would appreciate a test case.

The engine initializes local variables only at the beginning of a SP/trigger
(set them to NULL). It doesn't and shoudn't unexpectedly (without any
explicit assignment operator or SELECT ... INTO clause) change user
variables in the body of a procedure.

If a plain SELECT ... INTO returns nothing, then nothing is assigned to a
variable. And it's absolutely logical. Assigning any other value or NULL is
wrong. The only correct alternative way I can think about is throwing an
exception (like Oracle does).


Dmitry