Yep. It only works correctly if the conditions are "perfect" :). But I
sure will miss it! I'm highly considering creating a local fork of jooq
and customising some bits to suit my needs. That way I only have to
consider my immediate use case.
You'll have to explain the low-hanging fruit metaphor.
Thanks, Ryan
On 1/03/2013 1:39 AM, Lukas Eder wrote:
Just thinking it adds to the reasons not too put extra "smarts"
into JOOQ. I could turn MVCC off, but I pretty much rely on it to
avoid deadlocks.
This seemed like such a low-hanging fruit. But the more we think about
it, the more I'm inclined to deprecate optimistic locking entirely...
--
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.
