...
In a real repository pattern implementation, this would be handled in a very different manner. The interfaces for each data type would be separate, but behind the scenes they would be refactored and share data. For example, a single record could represent ReservationInfo OR AccommodationInfo OR QueueInfo OR a single "count" in the accommodation history. After all, each of those data types has SOME of the following elements:
- name
- (room) number
- week
... but never all three. So always the same type in a single table can be used, and viewed appropriately through the prism of the correct interface:
...