Which version of Derby are you using? There was a known issue with using functions in values clause inside a trigger in 10.0 that got fixed in later versions.
Satheesh Peter Nabbefeld wrote: > In the thread mentioned before, I've been told to use a function in a > VALUES clause. So I've asked 'CREATE TRIGGER ... FOR EACH STATEMENT > VALUES(...) doesn't work. Will I really have to insert a dummy value > into some dummy table to call a procedure or function from a trigger? ' > > Will I have to use 'DECLARE GLOBAL TEMPORARY TABLE ...'? And, as I > think autocommit is the default, will it be cleared automatically > after each INSERT? I'd prefer to have every inserted record deleted as > soon as possible, as it'd be used only as a dummy table, so memory > consumption should be as small as possible :-) . > > Kind regards > > Peter Nabbefeld > > >
