On Tue, Jan 19, 2010 at 3:37 AM, Siddharth Patnaik <[email protected]> wrote: > Hi, > I know how to do this in a RDBMS. If i were using a OR mapping > framework like hibernate i would have followed your apporach. However > in GAE we are not doing OR mapping at all. In java class annotations > we are not at all talking about Tables/columns etc etc. is n't it? We > just know about the objects/properties and relationship. In the > example we just know 2 objects User and Tour. I do not think we should > create a third object called Tour_User_Link and take care of > persistance/relationship management and querying ourselves. > Do you agree? or Am i missing something?
Well as this is not the AppEngine Java mailing list (if you are asking how to do this in Java, you should go there), I can not say, this is the generic AppEngine mailing list, as such I can tell you how it is done in the back-end, not Java, and in every RDBMS and ORM I have seen them do link tables behind the scenes as well. Even in a flat table system like GAE you still need a link table.
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
