Again, for my current project which involves a legacy database, I need
to map entities who have a one-to-one relationship. This translates to
the following: An entity "person", which is stored in a "person"-
table, always has one and only one SearcProfile, which is another
entity, stored in the "SearchProfile"-table. The Searchprofile also
has a one-to-one relationship with the Person.
As I understand, using One-To-One mappings is not advised. But what
would be the fitting strategy for mapping such a relation...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
