Subject Execute statement cant handle parameters which are NULL
Author ainpoissee

I'm using EXECUTE STATEMENT in trigger with two parameters like

EXECUTE STATEMENT (:Statement) (NEW_Alates := NEW.Alates, NEW_Kuni := NEW.Kuni) INTO :Count;

The problem is, that when either of the parameters is NULL then exception is raised:

Message: isc_dsql_execute2 failed
SQL Message : -901
Unsuccessful execution caused by system error that does not preclude successful execution of subsequent statements

Engine Code : 335544927
Engine Message :
Input parameters mismatch
At trigger 'ALLYKSUS_IU_CHKNAME' line: 27, col: 1

Is it a bug or this limitation is by design?