Hi,

We are using hibernate on a project I am working on and I can't figure out why it is saving certain data.

We have an Issue object, and each Issue has one associated ProfileVersion. This ProfileVersionshould *not* ever be saved by Hibernate. While we do need to save the Issue, all we ever need to do is read the ProfileVersion -- Never save it or update the ProfileVersion through Hibernate. What is the best way to ensure this? I have our configuration for the Issue object saying:

<many-to-one name="profileVersion" class="com.fifththird.cit.model.ProfileVersion"
fetch="select" cascade="none">


But still I see in the logs where hibernate is trying update statements on the ProfileVersion table, and this is busting our code. Thanks in advance if anyone can help, or just for taking the time to read my post! :],

Jim

Can you verify if any data in the ProfileVersion object is getting dirty before the commit is executed? If it is, then hibernate will certainly try to flush those changes using update.

Thanks for the feedback on this question! How can I tell if an object is dirty? I see an isDirty() method on the Hibernate session, but can I tell if individual objects are dirty? Thanks again,

Jim

I was also looking for isDirty at object level, but I couldnt locate. I will search more to find out that answer. Till that time, look into the hibernate logs. That would certainly tell you that for this class which fields have been detected by hibernate as dirty and with what values. Then you will have to debug your code/look into the code to see where it is happenning.
This is the easiest way that I know and which I use.

Hope that helps.
Thanks

Thanks for the help -- I'll look into that approach,

Jim