This is in the appengine transaction docs<https://developers.google.com/appengine/docs/python/datastore/transactions> ...
Note: If your application receives an exception when committing a transaction, it does not always mean that the transaction failed. You can receive Timeout, TransactionFailedError, or InternalError exceptions in cases where transactions have been committed and eventually will be applied successfully... Consider the following scenario 1. I update entity A within a transaction. 2. transaction operation results in the above described special "exception" where the transaction have been committed and eventually will be applied 3. I run db.get(entity_a_key_goes_here) within a transaction right after, or almost at the same time as step 2. *My Question:* Is it ever possible for the db.get() operation at step 3 above to return a stale value (or not the updated value set on step 1)? Are transactional db.get() operations guaranteed to return the freshest result even if the "weird" transaction exception occurs right before it? Thanks! I also asked this in stackoverflow<http://stackoverflow.com/questions/16998682/is-it-possible-for-a-transactional-db-get-to-return-a-stale-result-if-a-recent>, but I didn't get an answer. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
