There does not seem to be any need for a table with forumcategoryid and forumcategoryid. When a user creates a category/group, you have to update the corresponding category table/group table. As you have suggested, since the application is small it is far easier to handle issues, including column wise sorting, at client level.
J.Ganesan www.DataStoreGwt.com On Aug 14, 7:21 pm, MK Z <v5s12.msc...@gmail.com> wrote: > Hi, > Thanks for your reply. The category is not related to the group - category > holds value like Science/Tech/Music while Group stores value like > Teens/Kids/Adult. The reason I have these two fields I want to be able to > sort the forum according to category and follow by group. So in the forum > object I have (field1, ... fieldN, forumcategoryid, forumgroupid) and > forumcategory object (forumcategoryid, field1...) and forumgroup object > (forumgroupid, field1...). for small app, I think even without mappedBy > annonation in relevant class the application will still work. I just have to > tie up everything at app level, any advice? > > btw, ive gone through the links u given, but there isnt enough app-like > example on one-to-many relationship (only the simple guestbook example) > > > > > > > > java?hl=en. -- 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.
