I have a Player object that holds on to an Address object and use a many-to-one mapping as follows:
when I save my Player object, I want it to save the address object, hence the cascade="all" in the Player mapping. However the SQL that it generates is:
Why is it trying to do an update on the address object instead of an insert? Is there something I need to correct in the mapping?
Thanks for the help Brian
posted 11 years ago
Found the answer in another post, didn't look long enough. The unsave-value I had on my class definitions was using null, which was not correct since my ids were ints. I changed to unsave-value="0" and it worked!