I am working on an application which has a table with two related one to one tables in the existing design.
My research suggests that Entity Framework doesn't work well with an optional one to one relationship, and that isn't something they intend to change. So, I have the option of merging the tables, or making the optional tables non-optional if I want all of the information in one entity.
There's not a large amount of data, and it won't be heavily used, so I am not so much concerned about performance as design.
The data from the related tables, are not conceptually related to each other (or really the data maintained in the main table).
So, in this kind of situation, SHOULD I have a single entity? The optional data is just data, other than some minor validation and CRUD, there is no behavior. In fact, there is really no behavior in the whole app, it's just data.
