In a many-to-one relationship the relation is stored on the many side (e.g as an AddressId column in both the Person table and the Subsidiary table), so there's no problem there.
What if one of them moves? Well, that's a different problem. I guess you have to ask yourself if Addresses really deserve their own identity and table. /G On Dec 28, 2012, at 12:00 AM, Viktor Engelmann <[email protected]> wrote: > I thought that many-to-one meant multiple Persons OR multiple Subsidiaries > etc could reference an Address, but not both. > In this scenario, yes, subsidiaries of different companies could have rooms > in the same office building or so, so many-to-one really is a better idea. > > Then again, what if one of them moves? :-/ > Well, I'll figure something out for that scenario > > However, I will try this. Thank you very much :-) > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/nhusers/-/QaVhi4LFrbQJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
