I'm all for progress, but shouldn't you get transactions working correctly with one entity group first?
As far as I am aware, transactions can still end in a "this might have worked, or maybe not" state, requiring your actions to be idempotent, which is a mess and not close to being a decent solution. On Sep 1, 2011, at 11:20 AM, [email protected] wrote: > If you have trouble viewing or submitting this form, you can fill it out > online: > https://docs.google.com/spreadsheet/viewform?formkey=dGFzTUNrUExwOXpoVTA3X3RXSEF2VlE6MQ > > We're testing a new feature for the App Engine datastore: transactions on > multiple entity groups. We are looking for early testers interested into > trying this new feature and providing feeback to the engineering team. Feel > free to signup below if interested. > > > > -- > 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.
