I found something interesting: 1. The transaction is indeed atomic, as expected. So it does add the child and increase the parent version number. I saw this in the logs: I had added debug output that shows the version number immediately after the transaction finished.
2. However, at some point soon after the transaction finished, the version number is changed back to the previous one. IOW: it is decreased by one. But in my application, there is *no* code, *nowhere*, that sets or decreases the version number. So, this points to some other weirdness. Maybe some kind of rollback happens by a conflicting transaction, and that rollback goes wrong. Just an idea. But it would be weird in any case, since any conflicting transaction can only be one that reads from the data store. Any idea where to look? -- 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.
