Up to recently, in order to support pagination, for every non unique property say 'foo' I would also have a 'foo_index'. On put() I would set the 'foo_index' to a string value that had the same sort properties as 'foo' but was unique. All nice and fine, this had been described elsewhere, and does work. Now with the introductions of __key__queries it has been pointed out that there is a better way to do pagination and avoid the wasted 'foo_index' space, the extra work on update and the complex code. So I have been retiring the 'foo_index' fields. This also means that my queries that used to be:
'SELECT * .... ORDER BY foo_index' became 'SELECT * .... ORDER BY foo' Well, all this worked fine until during testing I realized that a few of the queries would return no results. Troubleshooting, led me to the conclusion that if the property name is 'date' then queries silently fail and return empty!!! I think I narrowed this down to the use of 'date' as field in the query (in particular I think is 'ORDER BY date' part). Now, calling a property 'date' is bad for other reasons so I renamed my fields and worked around the problem. I am curious, is what I report a bug or a feature (ie is date a reserved word in GQL)? Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
