Thanks for your replies. On 24 Feb., 20:02, theillustratedlife <[email protected]> wrote: > Don't type the ReferenceProperty. You mean subclassing the ReferenceProperty? I don't want to do that. Otherwise, I don't understand what you mean... > > You've got to be careful though. If you have A ref'ing B and B > ref'ing A, it's very easy to get stuck in a loop. (Anything that > recurses over the item's properties, like a for loop or the Django > debug page, will implicitly get the entity instead of the key for your > ReferenceProperty, causing an infinte loop). I understand the problem. But I would like to get to this point ;) Also, I assume there must be a solution for this because I cannot imagine that these sorts of references are not supported. They are so common. Think of two entities each holding references to a bunch of the other one. Even moreso References to self. Example: Person relation 1: parents 1-n relation 2: children 1-n Both going from Person to Person
On 24 Feb., 18:58, Mahmoud <[email protected]> wrote: > Hello, > Can you provide samples form your model definitions? It would make it > much easier to follow what you're trying to do. I will happiliy do so when I get to my work machine again. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
