Re[2]: [Hibernate-devel] Pessimistic locking?

[Doug C. <de...@fl...>]

> I went and had a good look on google to see how these terms are commonly
> used. Everyone agrees that optimistic locking means the application does
> some work by retaining a version number/timestamp and that pessimistic
> locking works by the database retaining a "lock" at read time. No-one seems
> terribly explicit as to whether a read lock constitutes a lock or not. I
> would have thought it did.

I agree.

> I would love to be sure of terminology here because when we come to
> document this I don't want to look clueless ;)

I notice that Benjamin Chi started a thread in the open discussion
called "Optimistic Locking with Versioning." I think that including
the word "Versioning" in any description of the Hibernate optimistic
locking feature will allay most confusion about what Hibernate is
doing. Both "Optimistic Locking with Versioning" and "Long Transaction
Support with Versioning" sound right to me.

e