When I went through reworking chapter 3, I deliberately left section 3.9 out of the review because I knew it deserved its own careful attention after M1.
- I think this section could be written in a somewhat more readable way.
- I don't quite understand why it says that we assume RC isolation but then talks a lot about dirty reads which are impossible in RC and has nothing to say about lost updates, which are possible.
- I also think the spec needs to clarify that what JPA calls
LockModeType.OPTIMISTIC is absolutely not what most people call "optimistic locking". The thing usually called "optimistic locking" prevents lost updates and allows non-repeatable reads.
I also wonder if we should say something more about what happens if the database itself is not in RC.
When I went through reworking chapter 3, I deliberately left section 3.9 out of the review because I knew it deserved its own careful attention after M1.
LockModeType.OPTIMISTICis absolutely not what most people call "optimistic locking". The thing usually called "optimistic locking" prevents lost updates and allows non-repeatable reads.I also wonder if we should say something more about what happens if the database itself is not in RC.