Hey Lukas, Thank you for your quick answer !
I'll take your advice and try to write a cache close to jdbc, your solution with jOOQ MockConnection seems promising. I will also wait for the new SQL rendering and variable binding SPI to enable the cache to be correctly cleared. As soon as I have something working, I will share it here ! Cheers Aurélien On Thursday, August 8, 2013 12:33:27 AM UTC+2, Ben Hood wrote: > > Hey Lukas, > > On Wed, Aug 7, 2013 at 10:58 AM, Lukas Eder <[email protected]<javascript:>> > wrote: > > However, to stay on the safe side, you might also think about using > > DB-messaging with triggers: > > http://stackoverflow.com/a/12619031/521799 > > Very cool - I can think of a few use cases for this. > > Cheers, > > Ben > -- 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.
