Your reply message has not been sent.
Your post was successful
> You could just throw an exception on PK update.I'm not so sure about that. The rest of the jOOQ API wouldn't throw
such an exception either. E.g., you could always explicitly update the
PK using Factory.update() or Factory.executeUpdate(), or plain SQL...
> Imagine if the PK has been updated in-between the fetch and store bySome databases will create a table lock when you update a primary key.
> another transaction. Then this could have disastrous behaviour. And it would
> break optimistic locking.
If not, you should SELECT ... FOR UPDATE such a record, if you intend
to change the primary key.
Anyway, best practices are not relevant for jOOQ (apart from the
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.