Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Shared vs regular editing contexts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Shared vs regular editing contexts

Subject: Re: Shared vs regular editing contexts
From: Sam Barnum <email@hidden>
Date: Mon, 9 Feb 2004 21:57:32 -0800

Only share entities that have no relationships to non-shared entities.
Oy vey! A major advantage of EOs in shared editing contexts is that you can connect them to objects in regular editing contexts without having to fault them in.

Here's a good rule of thumb -- don't use an SEC for objects that are going to change after you load them in.

Sorry, I wasn't very clear. It's perfectly fine to share an entity that has relationships _from_ a non-shared entity. The problems arise when you traverse a relationship from the shared entity to the non-shared entity. All the records returned by the relationship from the shared object will be registered into the shared editing context, which is most likely not what you want.

e.g. if you have Departments and Users, and want to make Departments shared, just make the relationship from departments to users not a class property, but keep the relationship from User to Department as a class property.

It's OK to share objects that will change, it's just a little extra work to change them. _______________________________________________ webobjects-dev mailing list | email@hidden Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev Do not post admin requests to the list. They will be ignored.

References:
	>Re: Shared vs regular editing contexts (From: Anthony Paras <email@hidden>)

Prev by Date: Re: Shared vs regular editing contexts
Next by Date: Re: Shared vs regular editing contexts
Previous by thread: Re: Shared vs regular editing contexts
Next by thread: RE: Shared vs regular editing contexts
Index(es):
- Date
- Thread