I don't think it would work that way, without mapping from Address to Employee, in one-to-many relationship, at least in my experiences.
Also, I don't think one-to-many relationship is what you want in your case. What you actually want is many-to-many relationship, so that it would behave the way you've described. This way, you would need another holder table with contains only primary keys from both entities: Employee and Address. On Tue, Apr 23, 2013 at 3:08 AM, Peter Forstmeier < [email protected]> wrote: > Hi, > there should de no mapping from address to Employee. > i would like to implement a sort of One-Way_mapping. > The idea behind this is to have one Addresstable for all my Entitys > like CusomerBillingAddress-CustomeHomeAddress, ProjectDeliveryAddress > and so on. > > Peter > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/nhusers?hl=en-US. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Regards, Maximilian Haru Raditya -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
