thanks guys for your suggestions. but having a separate entity holding the foreign key will make updates unusable for even moderate size relationships >1000.
i have used essentially the same approach suggested by nicole but each 'relational' entity will hold a list of foreign keys rather than a single key. this makes update significantly faster as i have less relational entities to update. This provides a solution to what google appengine guys call 'fan out problem'. hope this helps others. -lp -- 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.
