I've had experience which suggests otherwise :) I'm finding that very occasionally the entity returned by the read-by-key hasn't been updated yet. I've got around it by just re-queuing the task, and the second time around the entity is always in the updated state.
I must admit that I was quite surprised it was happening - at first I thought I must not have enqueued in the task in the transaction, but after checking I definitely am. -- 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.
