2 Classes: a Post and a Comment; there is a one to many relationship with one Post having many Comments
I’m thinking of a couple of options Option 1: The Post contains a list of keys to a Comment (and the Comment does not know directly about which Post it pertains to) Option 2: The Comment contains a key to its Post (and the Comment has no direct knowledge of Comments) In both cases, I would like to have the ability to query in either direction. I think that GAE would support that since (using Option 1 as an example) a Comment could always query for Posts containing its key in the MVC property. My question is whether there is a significant performance difference between querying in either direction. Note: I’m avoiding each class having a key to the other to avoid the need for a transaction boundary to maintain referential integrity. Would like to hear opinions. Thanks! ~Michael -- 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 [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-java?hl=en.
