Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 3
    You said that "joins are expensive." Is this the only problem you're having? Because if it is, there are easier solutions than turning your architecture upside down. Commented Apr 15, 2016 at 22:55
  • 1
    Also, for what it's worth, "normalization" is the relational database equivalent of the Single-Responsibility Principle. Normalization basically says "store each datum in one place, and one place only." Also known as "Single Source of Truth." Commented Apr 15, 2016 at 22:57
  • @RobertHarvey: Thanks. I just want to go with the standardized approach.... and I think I've found my answer: There is something called Table Splitting in Entity Framework, which allows me to map different Entities to a same Table, which will work perfectly in my case because that's what I think I need! c-sharpcorner.com/UploadFile/ff2f08/… Commented Apr 16, 2016 at 0:00
  • 2
    Code first isn't the standardized approach. It's just an approach. Commented Apr 16, 2016 at 0:47
  • I know this is old. I just wanted to comment back that one to one relationship is not EAV, which is what I was misunderstanding this time. Commented May 30, 2019 at 13:57