Only the enqueuing of the tasks is transactional. You should expect strong consistency in that situation. The task should not run unless the commit has succeeded. Transactional reads (default read) will "wait" to make sure the data is the new version before returning.
Did you find some documentation that would suggest otherwise? Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Fri, Apr 8, 2011 at 11:52 AM, Simon Knott <[email protected]> wrote: > I've asked this question before, but haven't had any official answers. > > What's the expected behaviour of the following on an HR app: > > 1. Carry out a put and schedule a task in a transaction > 2. Commit the transaction > 3. In the task, read-by-key for the entity you put in the transaction > > Should the entity read in the task be the updated entity, or is there a > chance that the task is run before the put has been committed fully? > > -- > 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. > -- 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.
