I have a question about collections in one to many relationship
my concern is extra queries and how to avoid them in a
desktop application.

for example Parent has more children

Parent p;
child c;

when I save Child and it has a parent defined
after flushing Parent in my session is not updated
so I update p.getChildren().add(c);

does any one know will this cause the collection to be
dirty and be saved upon next flush

I'm not sure if I explained my problem well,
but my goal is to keep the getChildren() collection
up-to-date and avoid unnecessary database access

need more info, read the red box again

I'm not posting a bug, but a general question.


Just need to know:

in the parent child relationship

should I expect Hibernate if i call
c.setParent();
to add the child "c" to the parents collection "p.getChildren()"


I tried something like this and it works only when I restart the application

Nope, you should not expect that. Hibernate associations behave identically to ordinary Java associations.

no, a best practice in java about bidirectionnal association is to manage both sides of the association, methods like addChild & removeChild are very usefull for this

thank you :)

now the second part of my question:

after
c.setParent();
and
p.getChildren().add(c);

If I save parent .. cascading will save the child also,
but I have little knowledge on how it happens actually
(I mean query count)


is there a link to an article that considers optimizing
while saving these objects (there is some in documentation),
or should I watch the log for queries and research it
for my case