Hi,
I have a login page and once the user is logged in i will add the user object in the servlet session.
This user table has one to many relationships with many tables. One of the table is EmploymentDetails.
One user might have more than one entry in employment table.
When the user wants to see the employment details, he will be taken to the employment details page.
So in the controller, i will do the following before taking him to the jsp page.

Part of the code :

usersDAO.attachClean(user); // Here i am attaching the user to the hibernate session.

Set<EducationalDetails> educationDetailsSet = user.getEmploymentDetailses();

Once the user is taken to the jsp page,

if i refresh the page again, the query is not fired as the data is fetched from the Hibernate session.
But, some one else has modified the data in between directly in the table.
But these modified data are not reflected in the JSP page as it still fetch values from hibernate session.

How to prevent this?

If i need to add session.refresh(), Will it trigger the query every time when i refresh the page?
If it is so, how to improve the performance as it has to hit the DB every time?

The Set<EducationalDetails> was generated by a tool. Can i modify it to List as i want the insertion order in the JSP?


Thanks,
Baskar.S

Is another application interacting with the database and modifying data? Perhaps you can avoid modifying the data except through Hibernate so that any changes to the data are visible to Hibernate.



Hibernate won't care if the EducationDetails is a list or a set, it'll handle either one, so you should have any trouble changing the collection type as far as it's concerned.

Thanks for your reply.

Sometimes database administrator may change certain fields directly in database.
And we also use schedulers that runs at specified intervals and modifies certain values.

If the scheduler can be run in the Java code through hibernate, that'll fix that problem. Same thing with the admin, if they can use a tool that goes through hibernate to modify the entities.

Thats great.
But still i am curious to know, How to handle if administrator changes data directly?