Yes, agree. Should be careful for different clients. Hibernate using JDBC batch mode update the database, so if there are some update come from other channel, should use hibernate timestamp to compare the consistency before the update. Actually, this one also happen in one clients, such as one web application, one client read the data for a while, and another guy already submit the change, when the first guy submit, normally we do not check whether the data been changed. (By the default isolation). Just my feeling.