Another Nibernate Call For Help - One-To-One

04 Jun 2008

I have a relationship which would normally be described as one-to-one. It's very similar to a Employee / EmployeeDetail relationship which you see used in many examples. My issue is that I'm working with legacy data, so the "child" part of the relationship, the EmployeeDetail, probably won't exist.

I'm struggling to understand how to map this. I know if it wasn't for the absent EmployeeDetails, this would be one-to-one. So I'm loathe to think about this in terms of another relationship type because as soon as the EmployeeDetail is available, it will be one-to-one again.

I'd appreciate any thoughts anyone out there might have.

Feedback or questions on this post? Create an issue on GitHub.