There is no transaction mechanism around memcache. Although it is technically possible to use an entity group (or groups) on the datastore to create a transaction mechainsm on top of memcache, it does not make sense to use slower mechanism (datastore) on top of faster mechanism (memcache).
Generally speaking, you should use memcache to return a "snapshot" of data to the client. If you need transactions, go directly to the datastore. Satoshi On Feb 1, 6:35 am, masterzim <[email protected]> wrote: > In official documentation I didn't find nothing about memcache > transaction. What happens if I access to memcache from different > request( this is save? ) , is transactions atomic? This will be great > if somebody can explain this. -- 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.
