The docs here use .run() - more like a .start()-like command: https://cloud.google.com/datastore/docs/concepts/transactions
However the direct reference: https://googleapis.dev/nodejs/datastore/latest/Transaction.html#run Uses .run(function(){ DO_THINGS_HERE_THEN_COMMIT }); kinda way So basically the App Engine examples use .run() like a formality, they just call transaction's get methods etc. afterwards - but the direct docs suggest everything to be inside .run() *Question:* I'm guessing .run() is like a formality that starts a transaction, the transaction.get()'s etc. lock entities, and if they are modified outside, transaction fails? - so basically, instead of a formality .run() - the other transaction commands could've internally done this too And I also guess retries aren't a thing any more, so using .run() like a formality goes - however, if the default approach was to put everything inside the run()'s callback function, couldn't there be a retry parameter too? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/c77de5c1-a20e-4b4d-88e5-7d21e95ba5f1n%40googlegroups.com.
