On Jan 1, 2006, at 9:53 AM, Miguel Arroz wrote:
Hi!
Imagine I have the following scenario:
- An entity "user".
- An entity "file".
- A many-to-many relationship between both.
Now, I want to store something like the access permissions a user
have over each file. The obvious way to do that is storing that data
in the relationship itself. What's the best way to do that in
WebObjects? The problem is that the userFile record is only created
when inserting the "user" and "file" records in the DB, so I cannot
access it (and change it) before a save. But if I save, I get an error
that I'm violating the non-null constraints. Of course, I may drop the
non-null constraint, but this seems a bit ugly to me...
How do you guys do this kind of stuff?
The obvious way is the correct way. In this situation, one cannot use
flattened relationships as one needs to access the relationship
directly. Other than that, there's no trick to it.
Set up User, File and UserFile EOs, create&instantiate all three, and
use addObjectToRelationshipWithKey to connect them up.
-arturo
_______________________________________________
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]
