Sounds good James. The owned relationship between Book and Chapter is just defined by the fact that Book has a collection of Chapter as a member variable. If the relationship is bi-directional (i.e. Chapter has a Book as a member variable) then you use the mappedBy field in the @Persistent annotation. Looking foreward to youre feedback.
On Nov 3, 2009 1:22 PM, "James H" <james.hollier...@gmail.com> wrote: Ok Bryce...I'm back. Going to test with your ideas now. In my case, I tend to avoid generic column names like "id" in favor of "bookId" and "chapterId" so I should not have any naming conflicts (at least rarely). Also, my FK embedded classes should not have any collections though I have a feeling they may come up as I get further into it. I'll just test with Book and owned relation Chapter as you have it here. How do we tell JDO whether a relation is "owned" vs "unowned" by the way? Because I would like to have a child object of each for the testing. Thanks! On Oct 9, 12:06 pm, bryce cottam <bcot...@gmail.com> wrote: > FYI, this video was hugely helpful fo... > On Fri, Oct 9, 2009 at 10:46 AM, James H <james.hollier...@gmail.com> wrote: > > > Ylmz, thats how... > ... > > read more ยป- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~---------... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
