Hi,

I'm encountering an issue where hibernate changes data on a read. In my application, I have hibernate save my data into a database. And then on a subsequent read, it seems to retrieve the data but resets the value columns before doing a read. For example, I have the following record saved to my CONTAINER table:



When I do the subsequent read, the table looks like this:



Any ideas why hibernate would change the values during a read? I'm totally perplexed right now. Thanks in advance!

-los

It wouldn't. Something else is going on. First check for triggers on the table; if that's not it, you'll have to examine your mappings and data access code to see what would cause that.

Thanks for the reply,

You're right. I realized that my setValue() method has a condition... it checks to see if the item is in stock. The issue now is, can I tell hibernate which order to populate the fields when doing a read? Here is my Item code:



Below is my Item table (w/inStock field):



When debugging the code, the inStock variable is false during the setValue call--telling me that the field did not get set before the call to setValue(). So I would like Hibernate to call setInStock before setValue when it reads from the DB. Is this possible? Thanks in advance!

-los

To do this, have a property (InternalValue) that you map in the normal way, with methods setInternalValue and getInternalValue. These are only in your impl class, not your interfance. In your impl and interface, have getValue() and setValue() methods that are not in your mapping file. Put the logic in setValue, and have setInternalValue do the raw, basic assignment.

This way, when hibernate calls setInternalValue(valueFromDB), there's no special code being called, and that's the correct way to do it: if it's in the DB, then it has already passed your special code in setValue(valueFromUser).

Never thought of this.

However, how would I go about doing this if the setValue method is actually an overriden one. For example, say my concrete class's setValue() has the logic built in, but the base class's setValue() is simple:



Know if I use hibernate's table per class hierarchy mixed with table per subclass for these three classes above with your suggestion, it would create duplicate columns-- one for BASE_ITEM table and the other for STOCK_ITEM table... I'm thinking of a hibernate mapping like this:



Hence the tables are not normalized since there will value and fake value, two columns to represent the same thing...


-los

Assuming that you are using the default access="property", the code you supplied is buggy. You must not refer to member values outside of the getter and setter methods.

Here's the rewritten code:As you can see, this requires no further correction: super.setValue() is the correct method to call, as it calls super.setIntervalValue(), which CGLib will have enhanced (if necessary). And the only thing you have to remember is that you must use the potentially-enhanced method to do the setting of any property; you must not skip the method call and set the member variable directly.