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

2023-11-29 Thread Rick Hillegas
You could replace the INSERT trigger with a generated column. I don't see how to eliminate the UPDATE trigger and preserve the behavior you want. Here's how to eliminate the INSERT trigger. First make the following class visible on the JVM's classpath: import java.sql.Timestamp; public

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

2023-11-29 Thread Steven Saunders
Hi Rick, Thanks for the alternative, it looks like you switched from Before Insert and Before Update to After Insert and After Update, respectfully. That will add multiple updates for one Insert or Update inturn causing unwanted triggers to fire in a slightly more complex schema I am trying to