On 5 May 2016, at 11:25am, Cecil Westerhof <cldwesterhof at gmail.com> wrote:
> At > the moment valid times can be marked as invalid and invalid times as valid. > Probably imposable to completely circumvent, but it can be done a lot > better. I don't know what TimeZone you're in (your surname looks German) but at this level of detail it becomes important whether you're in the US or EU or any other place. The phrase 'valid times' covers a large number of subjects and we can't tell which of them are important to you. For instance, do you care if someone enters a time which is skipped by the clocks going forward ? If at 1am your clocks skip straight to 2am, do you care if someone enters a time of 1:30am on that day ? Or maybe you're in Samoa, which skipped the 30th of December 2011 entirely, and may one day want to go the other way, which it would do by having a 32nd of December or an unwarranted 29th of February. You can get endlessly fussy about leap years and leap seconds and such things to the point where you know the Time Lords by name. SQLite definitely cannot handle that level of detail and it should not be used for timestamp validation. It's best either to find an external library for your programming language or tell yourself to relax and stop sweating the small stuff. Simon.
