Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

All DateTimes (e.g. AvailableOn, etc) should include a min date validation date/time frame from .. say .. 1900 <-> 2200 #2

Open
PureKrome opened this issue Feb 28, 2018 · 0 comments
Open

All DateTimes (e.g. AvailableOn, etc) should include a min date validation date/time frame from .. say .. 1900 <-> 2200 #2

PureKrome opened this issue Feb 28, 2018 · 0 comments

Comments

@PureKrome
Copy link
Contributor

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PureKrome