On 23.03.2008, at 01:11, Art Isbell wrote:
So add a unique constraint on the database level (to be safe) and
check for this condition in code (validateForSave) before saving to
the database.
Just use a compound primary key like a join entity, both being
propagated from the entities in the many-to-many relationship. This
applies the desired constraint without needing to actually add an
explicit constraint to the DB.
Hmmm. I actually don't like that for entities that are more than just
"join entities" with only two keys. Whether it works or not, I just
don't like the modeling. But that's my own taste, do what works for you.
cug
--
http://www.event-s.net
_______________________________________________
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]
