Hi everybody, To purge some user related contents, I am using a task which does a simple *keys only query* and then doing a *delete batch of the keys*. I am using a cursor if needed. The query is only defined by a *"kind"* filter and an *equality filter* on a *user ID* string field, *no sort order defined* (might be the reason of the problem described below).
I am testing *iterator.hasNext* to see if there is still some contents to delete. If it is the case I restart the same task with the current *cursor ID* as a parameter. I noticed pretty quickly that* iterator.hasNext* returns *false *even if some *data is remaining* and still need to be deleted. As a workaround I test if iterator.hasNext is true but a cursor ID parameter is defined. If true I restart the task without any cursor ID parameter and then all the remaining data gets deleted as wanted. Has anybody noticed such behavior? Is it documented somewhere? Any other solution? Thanx for your help. François -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
