I'd appreciate any ideas on this...

If I delete an object as follows:

session.delete( facility );
session.flush(); //not sure if this is necessary?
tx.commit();

then later attempt to load this object using:

session.load( Facility.class, facilityID );

The deleted object is found and loaded, instead of throwing a ObjectNotFoundException.

Note that this only happens if I specify a proxy for the Facility class. It fails properly with no proxy.

Also note that a session.find( 'from Facility f where f.facilityID = ?" ...) properly returns an empty set for that facility ID with or without a proxy.

I tried to evict() the object from the cache before delete()ing it, but this did not make a difference.

Is this a known bug or am I missing a step? Any ideas?

Thanks!
Michael.

This is expected, a lazy loading won't touch the DB unless it's needed. So inside a session, it has no way to know if the object has been deleted in another one.
Loading a non proxied object or doing find() will actually load the object and touch the dB.

Thanks for the info. I'll stick to using find().

What led me to believe that it was not correct behavior is that both the delete() and the load() were happening within the same open session with a disconnect() and reconnect() occuring in between.

I'll do some more experimenting to validate this.

thanks!
michael.

You could also use get()

I don't see a get() method in Session?

I do use a get(0) on the returned List object from the session.find(). This definitely works, albeit a bit more cumbersome than my original load() was.

Is there a more straightforward get() method somewhere that ensures a database check?

thanks,
Michael.

Hibernate 2.1 adds Session.get()