Re: [Hibernate] What would a good locking API look like?

In your environment, is no-wait something you use every time you select from a table, or is it something that is used very occasionally? What I mean is; is it enough to have a system property hibernate.locking.use_no_wait or mapping file option, or should I have a new LockMode LockMode.EXCLU

[Hibernate] What would a good locking API look like?

Hi, I've been thinking about improving Hibernate's locking API recently. Currently your object could be in 3 different states: * No lock, for example if you just called session.update(foo) or if the session was disconnected * Shared lock, for example if you just called session.load(id) or session.

Re: [Hibernate] patch to cirrus.hibernate.jmx.HibernateService

Put it in the patch manager if you like THanks Gavin - Original Message - From: "Chris Winters" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 01, 2002 12:42 PM Subject: [Hibernate] patch to cirrus.hibernate.jmx.HibernateService > I have a patch to cirrus.hiber

[Hibernate] patch to cirrus.hibernate.jmx.HibernateService

I have a patch to cirrus.hibernate.jmx.HibernateService to make subclassing easier. (In particular, it just changes all references to the mapping resources to method calls rather than direct variable accesses so that a subclass can define a different way to get the mapping files.) Should I submit