All DateTimes (e.g. AvailableOn, etc) should include a min date validation date/time frame from .. say .. 1900 <-> 2200 #2
Description
It's possible that a valid date/time value could be 1300 or 8 or 300 etc.. But sql server's (as an example) won't like that.
Sure, it's not good to assume that ORE will be only used by SQL Server .. but the point is, these date/time values should represent sorta-realistic ones. Not just any Date/Time.
For example, a rental property is not available on 1302 ... we're LONG past that. Nor is something wwaaay in the future.
So lets add some date/time boundary checks.
say ..
1900 -> 2200.