Re: Apache Derby CURRENT_TIMESTAMP not working in BEFORE INSERT and BEFORE UPDATE triggers at runtime

Hi Steven, Derby hews fairly closely to SQL Standard syntax. Your triggers look wrong to me. Your triggered SQL statements are VALUES statements, which simply manufacture some values and throw them into the void. I think that is why you had to include MODE DB2SQL in your syntax. I don't think

Apache Derby CURRENT_TIMESTAMP not working in BEFORE INSERT and BEFORE UPDATE triggers at runtime

Hi Everyone, I have several triggers I used in DB2 LUW, DB2 zOS, Oracle DB and MS SQL Server that set timestamp columns before inserts and before updates. When trying to do something similar in DerbyDB and use CURRENT_TIMESAMP the triggers deploy but at run time I get issues/errors detailed