Re: failing to provide new primary keys
Re: failing to provide new primary keys
- Subject: Re: failing to provide new primary keys
- From: Mike Schrag <email@hidden>
- Date: Tue, 18 Nov 2008 19:29:01 -0500
Doesn't everyone have inverse relationships on join entities?
They're required for flattening, and sort of annoying if you're not
flattening,
Except when you can't flatten as you're needing to store additional
info in the join.
Yeah, that was part 2 above, but i wrote it unclearly ... I meant it's
sort of annoying if you don't have inverses if you're not flattening
-- you have to-one's, so there's not much benefit to not having that
relationship there, but as I'm writing this I'm realizing you're
referring to the other side not the from-join-to-entity. So nevermind
anyway.
or maybe I'm not getting what you're saying.
I'm just saying in hindsight that it might have made more sense if
the option to propogate was on the entity needing the pk as an fk
(or its relationship with source as that fk) rather than where it is.
Oh, I agree .. It does seem sort of backwards. I get why they made it
like that, but it seems to perpetually confuse people.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden