Hi Marius, This is a great question. setUserRelationship is a Wonder / EOGenerator template addition.
setUserRelationship will do the job of adding your object to both side of the relationship. However, let's say the inverse relationship is pointing to tens of millions of other objects. If you revealed this array, you could use setUser to avoid the penalty of managing the flip-side of the relationship. However, in that case, you probably shouldn't reveal such an array as an attribute. -G On Aug 2, 2011, at 1:21 AM, Marius Soutier wrote: > Hi, > > one thing that's always confused me and which causes a bug every now and then > is for a given relationship, let's call it user, two setters are generated: > * `setUser(User user)` > * `setUserRelationship(User user)` > while only one getter `user()` is generated. > > When calling `setUser()`, the field in the database is populated, but EOF > doesn't understand the relationship was set which causes all kinds of weird > bugs. So what's the point of the `setUser()` method? > > Thanks, > - Marius > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/george%40boxofficetickets.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
