Re: [sqlite] Curious datetime/strftime BUG?

On 6/10/2014 18:35, Clemens Ladisch wrote: John wrote: On 5/10/2014 19:59, Clemens Ladisch wrote: The documentation says: | These functions only work for dates between -01-01 00:00:00 and | -12-31 23:59:59. For dates outside that range, the

Re: [sqlite] Curious datetime/strftime BUG?

John wrote: > On 5/10/2014 19:59, Clemens Ladisch wrote: >> The documentation says: >> | These functions only work for dates between -01-01 00:00:00 and >> | -12-31 23:59:59. For dates outside that range, the results of >> | these functions are

Re: [sqlite] Curious datetime/strftime BUG?

Sorry Clemens, but you have missed the point, the point being that the year component of the date string returned by strftime for -ve (or BCE) years are truncated to the -ve sign + the first three digits of the year. This is not the case for the result returned by date or datetime, which

Re: [sqlite] Curious datetime/strftime BUG?

John wrote: > -4713-11-25 12:00:00<-- 4 digit year > -471-11-25 12:00:00 <-- 3 digit year > -001-12-31 <-- 3 digit year > -001-12-31 <-- 3 digit year > -1975-10-21<-- 4 digit year > -197-10-21 <-- 3 digit year The documentation

[sqlite] Curious datetime/strftime BUG?

A week or so ago, someone posted about datetime(1) results not being the same as strftime("%Y-%m-%d %H:%M:%S",1) (sorry I have deleted OP msg) as per documentation. With: sqlite> .ver SQLite 3.7.13 2012-07-17 17:46:21 Of coarse, this may not apply to later versions. sqlite> select