You sure the index is identical?
On Tue, Sep 13, 2011 at 05:25, Ice13ill <andrei.fifi...@gmail.com> wrote: > I've been expecting the new datastore query improvement... > I have a question related to that feature: i have deployed a new > version with Java SDK 1.5.4 to test queries that previously failed, > but it seams they still fail immediately, also requesting an index > that is already built. Also, these queries work in Datastore Viewer. > Is it something i'm missing ? Do I have to delete the index and re- > built it ? > > > On Sep 13, 3:43 am, pdknsk <pdk...@googlemail.com> wrote: >> When will the docs for async memcache be added? I've got one >> particular question. >> >> In transactions, when you use db.put_async(), the transaction >> guarantees the put even if get_result() is not called. As I understand >> it, the transaction automatically calls get_result() for the put. >> >> How is this handled for async memcache? Unlike db put/get, memcache >> set/get does not raise an exception, but returns True/False. > > -- > 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. > > -- 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.
