Hi Dennis, Yes, in that case, triggers are clearly your best choice. As your database is still in a Java context (maybe even in the same process), it will be easy to wire back signals to the UI through some asynchronous messaging service - as simple as a ConcurrentLinkedDeque
Cheers Lukas 2013/3/11 Dennis Fischer <[email protected]> > Hi Lukas, > > thanks for that response. > I'm using H2 embedded database in this application, which seems to support > Java triggers (http://www.h2database.com/html/features.html#triggers) > It's probably best to use these instead of writing some custom > ExecutionListeners or something else - then I can get all events regardless > if jooq is used to submit these queries or if any other connection > possibility is used. > > Regards, > Dennis > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
