On Jul 25, 7:30 am, "Nick Johnson (Google)"
wrote:
> The first part specifically refers to ancestor queries. Ancestor queries
> always operate on the latest copy of the data, as they're restricted to an
> entity group; regular queries don't have that guarantee.
I understand that, but my problem
On Jul 26, 6:15 am, "Nick Johnson (Google)"
wrote:
> > I understand that, but my problem is with the indexes: even in the
> > scope of HR + transactions, the doc is confusing regarding wether or
> > not there can be a race-condition on indexes update.
>
> > For instance:
> > - transaction A modif
On Mon, Jul 25, 2011 at 4:30 PM, Pol wrote:
> On Jul 25, 7:30 am, "Nick Johnson (Google)"
> wrote:
>
> > The first part specifically refers to ancestor queries. Ancestor queries
> > always operate on the latest copy of the data, as they're restricted to
> an
> > entity group; regular queries don
