Ok, it looks as if I ran into this problem too. A parent has a lot of children.
I query a few children using some criteria instead of accessing them through a relationship. Can I edit 2 children and persist them using a single request? Any advice on how to deal with this would be greatly appreciated. On Jan 1, 11:31 am, Y2i <[email protected]> wrote: > This is interesting. Could you please share a more specific example? > > I haven't run into this problem yet. When I need to update multiple > entities, I enable their parent for editing and then persist the > parent. The children are persisted transitively, as described below: > > http://code.google.com/webtoolkit/doc/latest/DevGuideRequestFactory.h...http://code.google.com/webtoolkit/doc/latest/DevGuideRequestFactory.h... > > Are you editing multiple un-related entities? > > On Jan 1, 10:43 am, Daghan <[email protected]> wrote: > > > > > > > > > I have the same problem... I am going to google a solution but if I can't > > find one, I'll try to return a boolean for my persist() calls and try to > > delete the entities manually even they don't all succeed > > I guess I am just saying that I'll be mimicing the transaction logic on the > > client side... I don't like it -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-web-toolkit?hl=en.
