Johann,
it sounds like you got it the wrong way ’round.
Am 02.06.2008 um 08:58 schrieb Johan Henselmans:
I am creating a n:m relation between two tables, called adminuser
and admingroup, and flatten the relationship.
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.
The master-tables (adminuser and admingroup) have to propagate their
pk into the n:m (admingroupadminuser). admingroupadminuserhas no pk of
its own so it has nothing to propagate somewhere.
So you’ll have these real relationships (which you switch off in the
model):
adminuser <->> admingroupadminuser <<-> admingroup
and these two flattened ones:
adminuser <<->> admingroup
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.
This sounds strange.
I assume that turning off the propagate primary key would prevent
creating a new record in the n:m table admingroupadminuser.
See above.
Anybody has the same experience,
No.
solutions?
I hope so :)
atze
_______________________________________________
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]
