I'm developing a C# WPF desktop application where I need to read/write to an SQL database regularly. Now I want to map the data from the database to objects in C#. I can't use Entity Framework so I'm doing all my data access through Dapper, slapper automapper and stored procedures.

I know of this very similar question but I have ran into a problem with the mapping of some relationships.

As an example I have modeled this sample database

[![][1]][1] [1]: https://i.sstatic.net/DZO2p.png

The C# objects would look similar to this.

public class Manager {

   public string Name { get; set; }
   public string Phone { get; set; }
   public List<Facility> Facilities {get; set;}
} 

public class City {

   public string Name { get; set; }
   public string Description{ get; set; }
   public List<Facility> Facilities {get; set;}
} 

public class Facility {

   public string Name { get; set; }
   public string Description{ get; set; }
} 

The problem with this is that I now have 2 lists of Facility's, one in Manager and one in City with duplicate data. Facility could have many child tables, so this can be large amounts of data. Is there a better way to represent the data in C# or another design pattern?

I'm developing a C# WPF desktop application where I need to read/write to an SQL database regularly. Now I want to map the data from the database to objects in C#. I can't use Entity Framework so I'm doing all my data access through Dapper, slapper automapper and stored procedures.

I know of this very similar question but I have run into a problem with the mapping of some relationships.

As an example, I have modeled this sample database

[![][1]][1] [1]: https://i.sstatic.net/DZO2p.png

The C# objects would look similar to this.

public class Manager {

   public string Name { get; set; }
   public string Phone { get; set; }
   public List<Facility> Facilities {get; set;}
} 

public class City {

   public string Name { get; set; }
   public string Description{ get; set; }
   public List<Facility> Facilities {get; set;}
} 

public class Facility {

   public string Name { get; set; }
   public string Description{ get; set; }
} 

The problem with this is that I now have 2 lists of Facility's, one in Manager and one in City with duplicate data. The facility could have many child tables, so this can be large amounts of data. Is there a better way to represent the data in C# or another design pattern?

Im developing a c# WPF desktop application where i need to read/write to an SQL database regularly. Now i want to map the data from the db to Objects in C#. I cant use Entity Framework so Im doing all my data access through Dapper, slapper automapper and stored procedures.

I know of this very similar question but i have ran into a Problem with the mapping of some relationships.

As an example i have modeled this sample db

[![][1]][1] [1]: https://i.sstatic.net/DZO2p.png

The c# Objects would look similar to this.

public class Manager {

   public string Name { get; set; }
   public string Phone { get; set; }
   public List<Facility> {get; set;}
} 

public class City {

   public string Name { get; set; }
   public string Description{ get; set; }
   public List<Facility> {get; set;}
} 

public class Facility {

   public string Name { get; set; }
   public string Description{ get; set; }
} 

The problem with this is that I now have 2 lists of Facility's, one in Manager and one in City with duplicate data. Facility could have many child tables, so this can be big amounts of data. Is there a better way to represent the data in c# or another design pattern  ?

I'm developing a C# WPF desktop application where I need to read/write to an SQL database regularly. Now I want to map the data from the database to objects in C#. I can't use Entity Framework so I'm doing all my data access through Dapper, slapper automapper and stored procedures.

I know of this very similar question but I have ran into a problem with the mapping of some relationships.

As an example I have modeled this sample database

[![][1]][1] [1]: https://i.sstatic.net/DZO2p.png

The C# objects would look similar to this.

public class Manager {

   public string Name { get; set; }
   public string Phone { get; set; }
   public List<Facility> Facilities {get; set;}
} 

public class City {

   public string Name { get; set; }
   public string Description{ get; set; }
   public List<Facility> Facilities {get; set;}
} 

public class Facility {

   public string Name { get; set; }
   public string Description{ get; set; }
} 

The problem with this is that I now have 2 lists of Facility's, one in Manager and one in City with duplicate data. Facility could have many child tables, so this can be large amounts of data. Is there a better way to represent the data in C# or another design pattern?