OK, problem solved. My query was actually illegal, per the
documentation ("Properties In Inequality Filters Must Be Sorted Before
Other Sort Orders"). However, it worked just fine before the latest
push of the API code. Perhaps that requirement previously wasn't
being strictly checked, so the "bug fix" in the new API code exposed a
bug in my app.
Is there a list that the app engine team posts to before new code that
may affect application functionality is pushed? I didn't find out
about the problem until a user informed me that my app was down.
On May 9, 10:47 am, kiren <kirense...@gmail.com> wrote:
> FWIW, the offending query (which worked previously) looks like this:
>
> Debt.all().filter("user_from =", user.key()).filter("user_to !=",
> user.key()).order("-date")
>
> On May 9, 10:43 am, kiren <kirense...@gmail.com> wrote:
>
> > My app has been deployed for some time and was working just fine. Now
> > I am getting the following error:
>
> > Exception Type: BadArgumentError
> > Exception Value:
> > First ordering property must be the same as inequality filter
> > property, if specified for this query; received date, expected user_to
> > Exception Location: /base/python_lib/versions/1/google/appengine/api/
> > datastore.py in Order, line 803
> > Python Executable: /base/
>
> > Has there been a system change that may be affecting application
> > behavior?
>
> > Thanks in advance
> > Kiren
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
