Hi Mark, You only need to use Entity groups if you need to update multiple entities in a single transaction. Using them will not speed up insertion or querying. Using separate 'account group' and 'account' entity types, with a ReferenceProperty to connect an Account to its AccountGroup is probably your best bet here.
-Nick Johnson On Wed, Jul 15, 2009 at 6:01 PM, Mark Jones<[email protected]> wrote: > > I'm expecting lots of incoming data (about 80-90 million rows per day) > that needs to be broken across many "accounts" and will largely be > retrieved as a group on the account. > > I'm wanting to understand how to set up my entities and entity groups > so that the indexes are clustered around account in such a way that > ingestion and query are both fast. > > A total hierarchy looks like: > > Account Group - Queries across a group of accounts where the # of > accounts is small, and queries are few (other than to list the > accounts) > > Account - Date bounded queries filtered by one or two fields > > What is the correct structure for this kind of datastore. > > > > -- Nick Johnson, App Engine Developer Programs Engineer Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
