I saw the proposal for the Trigger2 interface (https://groups.google.com/forum/#!topic/h2-database/Sb3T1aVwoCE ) and thought if the community is considering something new around triggers, I'll bring back up a need we have: trigger after commit. The use case is that we have many processes that should occur when tables are updated. The most straightforward solution would be to install a commit trigger on the appropriate tables that publish an "updated" event on a bus that listeners can subscribe to. I brought this up earlier in this group https://groups.google.com/forum/#!searchin/h2-database/commit$20trigger/h2-database/huLqCpFQOhw/0pWXv82jriwJ
We have an item on our internal backlog to implement this functionality and contribute it back. I'm curious to hear comments from anyone who might find this kind of thing useful. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
