Hello.

When I have an object I just loaded using hibernate and after I load it was

deleted by another session (and commited there), do I now have a

reference to Null or just a transient object?

what will happen when I'll invoke a get() on one of its methods?

Thanks.

1. Session A loads row x into object X.
2. Session B loads row x into object X and deletes it and commits this change.

Session A knows nothing about the delete and assumes, that row x still exists in the DB. Every DB access for row x in Session A, let's say if X is a proxy, is likely to throw an exception.

HTH
Ernst

But if am using isolation level 2 (read commited) shouldnt I see the change?

Not unless you detach the object after every read, or at least after every transaction. As I understand it, isolation levels do not affect hibernate's session cache, only the jdbc connection.

The "Transactions and Concurrency" section of the ref docs is pretty thorough.

you have to call session.flush() (or session.refresh()) for synchronize your session with database (with commited state from another users) - this is same for every application, no only for hibernate - you have to see state in database

10x alot,

Now how can I know when a persistant object is no longer exist?

now Im doint refresh() and using the exception received.

Is there a better way?

you can try session.refresh(0 and get object again with session.get - get return null if object doesn't exists