Re: Many-To-Many Relationship across DB with different users
Re: Many-To-Many Relationship across DB with different users
- Subject: Re: Many-To-Many Relationship across DB with different users
- From: David Avendasora <email@hidden>
- Date: Thu, 15 Mar 2012 15:30:50 +0800
On Mar 14, 2012, at 11:47 PM, Ramsey Gurley wrote:
>
> On Mar 13, 2012, at 10:08 PM, David Avendasora wrote:
>
>>
>> On Mar 13, 2012, at 8:13 AM, Chuck Hill wrote:
>>
>>> It looks like the problem is the join table. Where does that sit? I suspect that Propogate Primary Key is not going to work across databases. You might have to manage that manually.
>>>
>>> Chuck
>>
>> Is this where I put my rant about the evils of join tables with compound PKs? Because it sure seems like it…
>>
>> Seriously though, Troy, I think this is a situation where you might be better off making the join table between Student and Teacher an actual Entity with a simple PK and separate FKs for Student and Teacher and get rid of propagate primary key. You can still flatten relationships for reading values, but EOF won't automatically create the record in the join table, but how hard is that to do anyway?
>
> I was reading about graph databases recently. They look to be designed explicitly to solve the problems you've described in previous emails about many-to-many relationships. Just thought I'd throw that out there :-)
Let's not go throwing the baby out with the bath water. Relational Databases are great, with the exception of the ability to use compound PKs. It's easy not to use them. You just . . . don't use them. Everything is fixed!
Dave
_______________________________________________
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