Hi,
I'm trying to understand which approach is better with regard to write
throughput in transactions.
We currently have multiple models that all use the same parent key.
As an example, we have the following models:
- Foo
- FooLog (which uses a parent key from Foo)
- FooAudit (which uses a parent key from Foo)
My understanding is that writes to FooLog, FooAudit and Foo are all on the
same entity group and thus there'll be limited throughput and possible
failed transactions.
We still want to be able to query in transactions, so a parent key is
required.
As a way around this, could we create a parent key using Foo's Id?
E.g.
FooLog would have Key("FooLog", foo.key.id())
and
FooAudit would have a key("FooAudit", foo.key.id()).
By doing this, Foo, FooLog and FooAudit would all be in different entity
groups, but I can still get consistent results when querying in a
transaction.
Is this the correct approach approach?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/c138ed6d-f001-4c6b-92f2-00cae57df52f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
