Hi Greg, db.put, as you suppose, is not atomic. If it were, transactions wouldn't have to be restricted to entity groups!
While it's probably marginally safer than individual puts - there are fewer things to break - you shouldn't rely on it for atomicity by any means. -Nick On Thu, Apr 21, 2011 at 9:59 AM, Greg <[email protected]> wrote: > Hi - > > I have some transactions that affect entities in two or more groups, > and so can't be wrapped in run_in_transaction(). This very > occasionally results in inconsistencies when one put() works and > another doesn't. > > It just occurred to me that perhaps using db.put() would be better > than discrete put()s for each entity. I assume db.put() isn't atomic - > if it was this would become far more useful than the limited > run_in_transaction(). > > But is db.put() significantly safer than multiple entity put()s? > > Cheers! > Greg. > > -- > 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. > > -- Nick Johnson, Developer Programs Engineer, App Engine -- 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.
