[sqlite] strftime accepts an illegal time string

2016-05-06 Thread Hick Gunter
> >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 ? > > >Simon. > Our local time skips from 2am to 3am and from 3am back to 2am for DST. T

[sqlite] strftime accepts an illegal time string

2016-05-05 Thread Cecil Westerhof
2016-05-05 17:09 GMT+02:00 Cecil Westerhof : > 2016-05-05 15:36 GMT+02:00 Adam Devita : > >> What would be the 'correct' behaviour for an out of bounds day in a >> month? If you look at dates as an index + natural number offset then Jan >> 32 == Feb 1.What is January 0 or January -1? >> > >

[sqlite] strftime accepts an illegal time string

2016-05-05 Thread Cecil Westerhof
2016-05-05 15:36 GMT+02:00 Adam Devita : > What would be the 'correct' behaviour for an out of bounds day in a > month? If you look at dates as an index + natural number offset then Jan > 32 == Feb 1.What is January 0 or January -1? > ?Well, if my memory is correct, that is the way MySQL d

[sqlite] strftime accepts an illegal time string

2016-05-05 Thread Cecil Westerhof
2016-05-05 12:39 GMT+02:00 Simon Slavin : > > On 5 May 2016, at 11:25am, Cecil Westerhof 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 Ti

[sqlite] strftime accepts an illegal time string

2016-05-05 Thread Cecil Westerhof
2016-05-05 10:08 GMT+02:00 R Smith : > > > On 2016/05/05 4:26 AM, Cecil Westerhof wrote: > >> The statement: >> SELECT strftime('%Y-%m-%d %H:%M:%f', '2016-04-31 17:19:59.670') >> gives: >> 2016-04-31 17:19:59.670 >> >> Should that not be NULL? >> >> It does with: >> SELECT strftime(

[sqlite] strftime accepts an illegal time string

2016-05-05 Thread Simon Slavin
On 5 May 2016, at 11:25am, Cecil Westerhof 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 le

[sqlite] strftime accepts an illegal time string

2016-05-05 Thread Stephan Beal
On Thu, May 5, 2016 at 10:08 AM, R Smith wrote: > seconds. Leap years themselves also have problems - the easiest check is > to see if the year is divisible by 4 and then allow a 29th on Feb, but of > course for the year 1900 this would have been wrong, but for 2000 this is > right again, etc i

[sqlite] strftime accepts an illegal time string

2016-05-05 Thread R Smith
On 2016/05/05 4:26 AM, Cecil Westerhof wrote: > The statement: > SELECT strftime('%Y-%m-%d %H:%M:%f', '2016-04-31 17:19:59.670') > gives: > 2016-04-31 17:19:59.670 > > Should that not be NULL? > > It does with: > SELECT strftime('%Y-%m-%d %H:%M:%f', '2016-04-32 17:19:59.670') > > I

[sqlite] strftime accepts an illegal time string

2016-05-05 Thread Adam Devita
What would be the 'correct' behaviour for an out of bounds day in a month? If you look at dates as an index + natural number offset then Jan 32 == Feb 1.What is January 0 or January -1? If expressing dates this way (and not as an int from an epoch) I think that it is up to the application t

[sqlite] strftime accepts an illegal time string

2016-05-05 Thread Cecil Westerhof
The statement: SELECT strftime('%Y-%m-%d %H:%M:%f', '2016-04-31 17:19:59.670') gives: 2016-04-31 17:19:59.670 Should that not be NULL? It does with: SELECT strftime('%Y-%m-%d %H:%M:%f', '2016-04-32 17:19:59.670') It looks like a value of 31 is always allowed for day: SELECT strft