其他 - C＃/ EF Core：处理（历史）日期/期间

给定一个使用ASP.NET Core Mvc和SQL Server和EF Core的C＃网站。

对于一个爱好项目，我正在寻找旧报纸，文件并寻找特定的建筑物。每次我找到此类建筑物的信息时，我都会尝试写下日期信息。这样我就可以跟踪这座建筑物在哪个时期。

假设我碰到Build X并看到了日期1880。我写下了date 1880。几周后，我再次遇到了X楼，看到日期：16/03/1877。我现在知道建筑物可以肯定地从16/03/1877到1880。

期间：16/03/1877-1880

• Now some buildings don't have any date info.
• Some buildings have only a single date (maybe with extra research another one could be found)
• Some buildings might have information that it existed in the 17th century (without a specific year or date).
• dates can contains year, year+month or year+month+day

Now what would be the best to store this in the database and represent this in a model.

Would 2 properties on a model be sufficient?

public class Building {
[DataType(DataType.Date)]
        [DisplayFormat(DataFormatString = "{0:yyyy-MM-dd}", ApplyFormatInEditMode = true)]
  public DateTime? Date1 { get; set; }
[DataType(DataType.Date)]
        [DisplayFormat(DataFormatString = "{0:yyyy-MM-dd}", ApplyFormatInEditMode = true)]
public DateTime? Date2 { get; set; }
}

Would it be suitable for search filters on the website. E.g. searching everything between 1830 - 1930 or everything from 17th century.

With the last question, I mean, how would you write a linq query if there is only one date given for a building (e.g. 1835). Would each query contain an extra check for the nullable date in case there is only a single date given? or are there better scenarios?

.Where(x => x.Date1 != null && x.Date1 >= 1830 && (x.Date2 == null || x.Date2 <= 1930))

Or is saving a DateTime? object not a good idea and better to store a short or integer and only keep track of the year component (if any)?

查看更多