On Thursday, January 6, 2011 10:06:03 PM UTC, Ikai Lan (Google) wrote: > > > In the original benchmark, you might notice that query performance across > entity groups is significantly faster - that's because queries assume > eventual consistency and are not executed in a transaction like get-by-key > operations. >
Is this right? The documentation states that STRONG_CONSISTENCY is the default (and this matches the code in the SDK): http://code.google.com/appengine/docs/python/datastore/queries.html#Setting_the_Read_Policy_and_Datastore_Call_Deadline Also, the last paragraph on this page contradicts itself: "A configuration object can be used any number of times. You must create a separate configuration object for each datastore call that uses it." And further up the page in the section "Queries and Indexes" the link and explanation of KEY_RESERVED_PROPERTY is Java-specific. -- 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.
