Officially, there is no guaranteed upper bound for queries to become consistent. In practice it's usually a second or two, but infrastructure failures could in theory extend the period to minutes or hours or (gasp) days.
One thing worth noting: If you access the datastore in ReadPolicy.Consistency.EVENTUAL mode, get-by-id will be eventually consistent just like queries. And it's *dramatically* faster, ~1/5 latency in my recent experiments. Jeff On Tue, Feb 14, 2012 at 12:15 PM, Mahron <[email protected]> wrote: > get_by_id or GetObjectbyID are supposed to always be consistent. > Basically all Items returned by query or id are up to date. If it is > not, there is a serious problem. > > "Sometimes the Query returns the value updated, sometimes not." By > that I suppose it does not return the entity at all. If it returns a > version different than after the last Put(), then I am pretty sure > that's a bug. > > -- > 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. > > -- 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.
