According to the LR, Date.TotalSeconds should be positive for dates after 12:00AM, January 1, 1904. This doesn’t seem to be the case for me.
I made a check in my code to exclude some odd dates that somehow slipped into my database (Year 2), so I tested against total seconds, only allowing posts with positive totalseconds to be used. For some reason NOTHING slipped past that test. It turns out TotalSeconds is also negative for the current date.
As you can see from this screenshot from the debugger, something strange is going on here, as the date is both october 30th and october 13th in that Date.
Yes, it’s Sqlite, so it could be a bug in the sqlite implementation.
It’s not really a big deal for my app, as it’s just as easy testing on Year as totalSeconds. I just happened to use it that way, when I discovered this “issue”.
As far as I can tell, there are no problems with Date anywhere else.
Could it be that the regional settings of the computer could cause display problems? If i look at Joseph’s picture of his date program i see that the totalseconds is displayed as a large integer while if i run his example program i see the totalseconds displayed as a floating point number. To me it feels like inconsistent behaviour.