Subject | UDF - module loading and unloading |
---|---|
Author | Daniel Albuschat |
Post date | 2005-03-11T22:44:46Z |
Hello,
I've just tested how module loading/unloading of shared objects/dlls for UDFs
is handled. It seems that the module will be loaded on the first use
of an UDF from it,
and unloaded when the conncetion (transaction?) that the UDF was using, closes.
But well, is the behaviour of FB regarding this issue documented somewhere?
Is it the same on *NIX and Windows? I don't have access to a windows box atm.
When an UDF is called from within a trigger, is it "associated" with the
connection that caused the trigger to fire?
My point is that I would like to keep initialising and deinitialising
as small as possible. One time per transaction would be small enough,
though.
Thanks,
Daniel
--
eat(this); // delicious suicide
I've just tested how module loading/unloading of shared objects/dlls for UDFs
is handled. It seems that the module will be loaded on the first use
of an UDF from it,
and unloaded when the conncetion (transaction?) that the UDF was using, closes.
But well, is the behaviour of FB regarding this issue documented somewhere?
Is it the same on *NIX and Windows? I don't have access to a windows box atm.
When an UDF is called from within a trigger, is it "associated" with the
connection that caused the trigger to fire?
My point is that I would like to keep initialising and deinitialising
as small as possible. One time per transaction would be small enough,
though.
Thanks,
Daniel
--
eat(this); // delicious suicide