Home/ Questions/Q 6787991
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T17:25:54+00:00

I have determined a relational model makes more sense for a particular collection in

  • 0

I have determined a relational model makes more sense for a particular collection in a database. The problem is, the domain model was originally started with an embedded model and there is a large amount of UI code that expects it to be in this form. Updating the database schema isn’t an issue, but I’m curious if there is any easy way around remodeling the C# domain objects to a more old-fashioned relational model. I’ve started writing mappers (with AutoMapper) between version one and version two (see classes below), but it’s getting messy really quick.

Below is some fictitious code that outlines a similar domain model.

// Existing
class MyClass
{
    List<Event> Events { get; set; }
    List<Movie> Movies { get; set; }
}

// How it should have been modeled
class MyClass
{
    List<int> Events { get; set; } // Stores Event IDs
    List<int> Movies { get; set; } // Stores Movie IDs
}

The database will have to be normalized.

If I have to remodel the domain model, that’s fine; I just want to feel comfortable I’ve exhausted other possibilities that might save time. Is there an easy solution to this problem I’m overlooking?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Given the specific problem, it seemed the only two options I could justify were the two I mentioned in my initial post (map the data manually or change my domain object). Ultimately, for me, the path of least resistance was to map the data manually. I appreciate the suggestion by pjvds, but I couldn’t justify switching to a new ORM at this stage of the project considering so many other things work better with the C# MongoDB driver and also considering a mapper isn’t necessary for the other portions of our database.

    • 0