> Related: why are child objects not automatically detached if the > parent is detached? Would that not not logical?
JPA doesn't have "fetch groups" as such, just a "default fetch group". This is defined by which fields are EAGER loaded. So if you had your field marked as EAGER then it would be detached. By default 1-N fields are LAZY hence not detached. The reason we don't just detach child objects is that of where do you stop ? Detach a full object graph ? That'd hammer the performance on some graphs, hence done using the fetch groups etc. Try accessing the field before the detach. The log will tell you whether/when it is detached. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
