Hi Ryan, > [...] > I was going to use this to fire before a transaction was committed so extra > validation could be done in the application.
Thanks for your input. Yes, that downside is really the actual problem here. Not only will stored procedure calls bypass your jOOQ-specific logic, but also plain SQL calls, calls from other (non-Java/jOOQ) applications and the MERGE / INSERT .. ON DUPLICATE KEY UPDATE statements are hard to predict, too In the mean time, there had been some more discussion on this Stack Overflow question, on which I have put a small bounty: http://stackoverflow.com/q/12618915/521799 It looks like the most reliable solution is really to handle these events in the database somehow, using triggers and then preferably a proprietary notification mechanism, or some sort of sophisticated polling...
