I was playing around with Hibernate for a little while. I'm just a rookie.
Everything went ok until I got into the need for some very basic but specific thing to be done that i couldn't ... so I'm asking you guys if it is true what I read in some forums that this behaviour is not fully supported by hibernate right now.
Here is the thing.
Suppose I have the following tables:
So there are proyects that can have pieces. There are color catalogues for each proyect, and the pieces of each proyect may or may not have a color.
Please note the foreign keys that are in the color and piece table, especially in the piece table, because is a composite one, that ensures that pieces of a certain proyect can have only colors that belong to that proyect's catalog.
The point is, i did everything to get to the point: session.save(piece) and attributes are updated well.. but when i change the id of the color to another or just set the id to null is not working. No error, just not working.
So, does Hibernate is prepared to handle this situation?
Thanks in advance!
If you have a bad day in October, have a slice of banana cream pie. And this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!