-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Closed
Labels
bugConfirmed bugs or reports that are very likely to be bugs.Confirmed bugs or reports that are very likely to be bugs.
Description
Details for the issue
Just found this on the Debian bug tracker
I have a sqlitefile with timestamps and some data values. When I plot the
data vs datetime with the builtin plot function, I get a weird outlier when
the datetime is 2006-03-26 02:00
A minimal example is here:
http://www.nmdb.eu/~steigies/debian/NEWK_2006_1h.sqlite
This also happens when I change the minute to other values as long as the
hour stays at two. I did not specify a timezone in the datetime, so if I understand
http://sqlite.org/lang_datefunc.html
correctly, this is taken as UTC.
March 26 was the beginning of Daylight Saving Time in
most of Europe, the hour between 2 and 3 does not exist on this day:
http://www.timeanddate.com/time/dst/2006.html
slitebrowser changes the datetime for this hour to ~ the year 2100 when
plotting the data. When I change my timezone from Europe/Berlin to
America/New_York, this glitch in the plot happens on April 2nd, the day DST
began in the USA.
I think sqlitebrowser should plot the data as given in the file, without
shifting values during DST switch to the year 2100 if I give it data in UTC.
If I specified a timezone, I do not expect the data to appear in 2100
either, mabye that data should be dropped from plotting, with a warning
given to the user instead.
thanks,
Christian
I'm still able to reproduce this with the latest version. It's also highly unlikely that this is a Linux-only bug.
Useful extra information
I'm opening this issue because:
- DB4S is crashing
- DB4S has a bug
- DB4S needs a feature
- DB4S has another problem
Metadata
Metadata
Assignees
Labels
bugConfirmed bugs or reports that are very likely to be bugs.Confirmed bugs or reports that are very likely to be bugs.