Hello, everyone. I've been stuck on an issue with app engine for quite a while now. I've got a rather complex set of changes that I want to bundle in a transaction but the logic of the changes is in many places dependent on what changes were made earlier. It seems that changes made earlier in a transaction are not visible even to the transaction code itself until its committed. Is there a way to circumvent that? I've tried breaking things down into smaller less logically confusing transactions but such efforts inevitably end up being impossible to rollback if an error occurs later.
I don't know what to try short of copying the entire entity group to some dummy objects and writing it back when I'm done. What's the reasoning behind this behaviour anyway? Its certainly not how other transaction systems work... Thanks in advance, Richard. -- 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.
