Heh. There isn't really. At the point in time that commit occurs, the rows has already been written into binary format, so there would be nothing to pass to the trigger.
What might be possible is to create a special kind of trigger that fires on a commit. Then you could probably use a combination of a normal trigger and a commit trigger to do what you want. For that, I think the Session class is where you want to start. On Friday, 19 April 2013, Mark Addleman wrote: > To Thomas or any other h2 committee : we'll gladly submit a patch for a > commit callback feature if you give us a hint where to start. > > -- > 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] <javascript:;>. > To post to this group, send email to > [email protected]<javascript:;> > . > Visit this group at http://groups.google.com/group/h2-database?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
