Tim is correct. Oliver, it sounds like this is related to the same behavior which you mentioned in this thread:
http://groups.google.com/group/google-appengine/browse_thread/thread/dc12949aca652f0c Good question, Jeff On Mon, Jun 1, 2009 at 11:05 PM, Tim Hoffman <[email protected]> wrote: > > Actually I got a sneaking suspicion it isn't > > Remember ReferenceProperties work on Kinds not Kind and Class used in > PolyModels > I would imagine you need to further filter the reference set so as to > only include the specific members of a > polymodel > > You probably need to put together a PolyModel aware version of > ReferenceProperty > > T > > On Jun 2, 9:31 am, Oliver Zheng <[email protected]> wrote: > > I am noticing this behaviour (which I think is a bug): > > > > class A(PolyModel): > > pass > > > > class B(B): > > a = ReferenceProperty(A, collection_name='b') > > > > class C(A): > > a = ReferenceProperty(A, collection_name='c') > > > > a = A() > > a.put() > > > > b = B() > > b.a = a > > b.put() > > > > c = C() > > c.a = a > > c.put() > > > > Now, a.b returns b and c, and a.c returns b and c as well. Is this the > > expected behaviour? I very much suspect this is a bug. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
