Yeah, realized the diff mechanism takes care of what problems I was thinking of shortly after posting, doh. It does mean, you can set a relationship you never retrieved with with(), but you can not un-set (null) a relationship unless you retrieved it, of course, who cares..! (and I didn't check this)
On Sat, Sep 24, 2011 at 12:05 AM, Thomas Broyer <[email protected]> wrote: > No, RF does a diff between the object you retrieved (unmodifiable, passed to > context.edit(obj)) and the one you're editing (returned from > context.edit(obj)) at the time you fire() your context, and sends that diff > over the wire. If you didn't retrieve a property and fills it on the > client-side, it'll see that you filled it and will send it to the server. > The only exception is ValueProxy: every single property in a ValueProxy is > sent, no diff is made, each ValueProxy instance is a distinct "value". > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/szisuiWUylIJ. > 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. > -- 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.
