That would result in an n:m table, admingroupadminuser, with two relationships on both sides: one would propagate the primary key to the table admingroupadminuser, the other one would be a flattened one to the other table.
However, I am now getting verification errors in EntityModeler after creating the table. It says:
The relationship adminGroupAdminUsers is a to-many but also propagates its primary key.
I assume that turning off the propagate primary key would prevent creating a new record in the n:m table admingroupadminuser.
Anybody has the same experience, solutions? Regards, Johan Henselmans http://www.netsense.nl Tel: +31-20-6267538 Fax: +31-20-6279159
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
