Well, you could head over to the JIRA issue site (see
www.hibernate.org for the link), but I'd expect it to be turned down. It's not really something that fits into hibernate's way of thinking. Hibernate won't lock rows for updating prematurely: if you have a massive update loop, no DB locks are acquired until you eventually flush. So the only time this is likely to be an issue is if some other app is writing to the DB. Still, no harm in trying, and I can't profess to know anything about the development team's vision for hibernate.