Handling database update outside of Hibernate

sterno · **Joined:** Fri Aug 12, 2005 1:08 am **Posts:** 1

I'm using Hibernate 3.0 and I'm trying to figure out exactly what I need to configure to permit the following:

1) Have a user, through hibernate, update and commit changes
2) Have a user, not through hibernate access those changes directly in the database and make changes
3) Have the hibernate user be able to view the updates that the non-hibernate user made

What I find right now, using MySQL, is that if I access the database from hibernate, and load a piece of data, the data never seems to refresh against the database. I'm running a query and the calling the list() method to get the object I'm referencing.

Any suggestions on what I need to do to force Hibernate to check the database when it loads an object?

jdl · **Joined:** Thu May 26, 2005 2:08 pm **Posts:** 99

Please fill out all of these fields that you deleted. Otherwise, we're just guessing what your code does.

Quote:

Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version:

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:

scesbron · **Joined:** Thu Sep 04, 2003 8:23 am **Posts:** 368

With your use case there is only one problem with second level cache. If you update the db outside hibernate it will be difficult to use the second level cache.

Also note that a session is a unit of work. It is often equals to a transaction. So if you open your session before you do your update outside hibernate, depending on your isolation level you may not see the changes you made in another transaction.

If this is not your problem, send a snippet code that show syntacticaly what you want to do