Passing the "many" objects through a single db.put is probably the
fastest way you can store separate entities. I believe there's still
a relatively linear cost for putting some number of entities, so it's
slower than doing a single entity put.
The performance will depend on how many is "many" o
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://gaesq
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 separa
