Is there a reason you havent posted this as a suggestion via the issue tracker
http://code.google.com/p/googleappengine/issues/list On 20 February 2010 06:43, notcourage <[email protected]> wrote: > Nestable/embeddable entities would be used to build graphs of entities > which are serialized inside a single entity. Protocol buffers support > nesting & repeating but not arbitrary graphs. > > Possible API additions: > * constructor: new Model(nest=parent) > * property type: NestedReferenceProperty; supported in lists. > * custom index support. > > Existing options for representing a Contact: > 1a) Contact entity w/ ListProperty's: addresses, emails, etc. > 1b) Contact entity w/ address1, address2, address3, email1, email2, > email3, etc. properties. > 2a) Contact entity w/ addresses property listing keys of Address > entities. This is a workaround because lists of ReferenceProperty is > unsupported. > New options: > 2b) Contact entity w/ addresses property listing > NestedReferenceProperty referencing Address nested entities. > 2c) Contact entity & Address nested entities--query by ancestor. > > -- > 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. > > -- 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.
