We saw this error yesterday too, but only for one of our users. The
query succeeds for everyone else...
(We were doing a fetch instead of a count, but otherwise it seems
pretty similar)
On Jan 8, 11:48 am, Ryan W wrote:
> All of a sudden this morning, I began getting this error in my app,
> wh
hi guys! "merge join" queries like these, ie queries that have equals
filters on multiple properties but no inequality filters or sort
orders, *usually* don't require an index. that's described in
http://code.google.com/appengine/docs/datastore/queriesandindexes.html#Defining_Indexes_With_index_ya
Thanks for the explanation. I was trying to avoid any
__search_text_index indexes as you suggest, to get around the 1 per
each number of keywords, so I didn't use any equality or sorts. It
usually works fine, and is again today as far as I can tell. It
must've been been something with the parti
I thought I would post our findings and solution. Our issue seems
slightly different.
We had entities similar to the following:
class Account(db.Model):
...
class AccountEntry(db.Model):
account = db.ReferenceProperty(Account)
tags = db.StringListProperty()
utime = db.DateTimeProperty()
