I'm looking for some general advice on the best way to proceed with my particular design.
I have a database in which most tables have a CreateDate and a RemoveDate field. Nothing from these tables will ever be deleted, only given a RemoveDate. The application driving this database will have a calendar visible at all times where the user can choose the current date. Only records that were valid on that date (CreateDate is before or equal and RemoveDate is null or after) will be displayed. So as the user moves around the calendar, the database will always look as it did on that day.
There's no problem listing objects based on the dates using a criterion. The problem is with collections, which are automatically loaded.
What is the cleanest way to go about this?
Cheers
|