Hello, Can you provide samples form your model definitions? It would make it much easier to follow what you're trying to do.
On Feb 24, 12:01 pm, simpsus_science <[email protected]> wrote: > Hallo, > > I read up the solution for implementing 1:n relationships by placing a > ReferenceProperty on the "n" part and naming the collection_name the > name you want to appear in the "1" part. > > I have a datamodel with hierarchical inheritance. > For Some Element D I want to have a 1:n relationship to a more generic > type (and its subclasses) A. > So I have to put a ReferenceProperty to A naming D as the type beeing > referenced. > > This doesn't work because D has not been defined when its named as a > type for the reference in A. > I can't put the definition of D in front of A because the superclass > of D has not been defined then (or is A, to keep it simple). > > Is there any solution for my problem? > > In Java, I would declare D prior to using it in A, but define it at > its appropriate place. I don't know if there is a sulotion in an > interpreted language.... > > Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
