Perhaps if I create the one-to-many relationships using reference properties and put all of the models of the "many" objects using a single db.put then performance may not be an issue.
Is this a good assumption? On Dec 6, 8:58 am, kang <[EMAIL PROTECTED]> wrote: > maybe this helps:http://gaesql.appspot.com/ > > > > On Sat, Dec 6, 2008 at 9:54 PM, lawnman <[EMAIL PROTECTED]> wrote: > > > Is it possible to have a class based on db.Model that contains a list > > of other classes also based on db.Model but where the second classes > > are not stored in the Datastore separately but rather are stored with > > the first class. In other words I want a one-to-many relationship but > > do not want to store the "many's" as separate transactions for > > performance reasons nor do I want use entity groups because I do not > > have a need to reference the "many's" outside of referencing the > > "one". > > > for example: > > > class entity(db.Model): > > name = db.StringProperty() > > > class one(db.Model): > > entitylist = db.??? where ??? defines a list of entity. > > > Thanks, > > -- > Stay hungry,Stay foolish. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
