Is it OK to have both a Reference relationship and a Parent relationship between two objects?
For example: I have a situation with an object Y, an object S, and a bunch of objects AR. All AR objects need to reference Y (to easily get all ARs relating to Y). Some of the AR objects belong the Y entity group (they are updated by one set of users in one context), while some of the AR objects belong to the S entity group (updated by another category of users in a different context). Is it OK to create AR entities where some have referenceproperty = y, and ancestor = y; and others where referenceproperty = y, and ancestor = s I'm assuming it is OK - but any time I encounter redundancy, I start getting paranoid... :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
