This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm writing a hibernate application and I'm using hibernates automatic version checking to ensure that my transactions are properly isolated from each other. I'm doing this by adding the version property in all of my classes. Is this enough or do I also need to set an isolation level in my application? For example
I like automatic version checking, because it does not use locks.
I don't like to set an isolation level because it introduces locks.
Is it a good idea to mix optimistic and pessimistic transaction isolation. Or is it overkill?