I'm struggling with a data inconsistency issue (something that is supposed to be saved atomically is not) and it might got to do to with how I use transactions.
Would love to clarify if my usage is flawed in any way: *Use case*: Making changes in couple entities and need to ensure they are saved atomically. In other words, if one entity fails to save all entities should rollback the changes. *Environment*: Java standard env using ofy() *Data model*: User (Cached entity using ofy()), Task (child of User, each User can have multiple Task instances) *Usage*: 1. load couple User and Task entities (User by key, Task(s) by query) 2. make changes to fetched entities from #1 3. Starts a transaction that only does a save() on all entities from #1 (all belong to the same group) I'm expecting #3 to save all entities atomically but at times some entities still hold old values while others in the same transaction are not. Does the above usage make sense? or is there any requirement that #1+#2 will reside within the same transaction in #3? -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2657da22-f904-44eb-9d0e-a61826407226%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
