我觉得我的那个帖子不是新手帖是一个事实在在的技术问题,也可能是很多人没有注意到的

HQL UPDATE statements, by default do not effect the Section 5.1.7, “version (optional)” or the Section 5.1.8,
“timestamp (optional)” property values for the affected entities; this is in keeping with the EJB3 specification.
However, you can force Hibernate to properly reset the version or timestamp property values through the use
of a versioned update. This is achieved by adding the VERSIONED keyword after the UPDATE keyword.
Session session = sessionFactory.openSession();
Transaction tx = session.beginTransaction();
String hqlVersionedUpdate = "update versioned Customer set name = :newName where name =ldName";
int updatedEntities = s.createQuery( hqlUpdate )
.setString( "newName", newName )
.setString( "oldName", oldName )
.executeUpdate();
tx.commit();
session.close();
Note that custom version types (org.hibernate.usertype.UserVersionType) are not allowed in conjunction
with a update versioned statement.

希望管理员以后可以认真考量问题的技术含量!再次谢谢!