https://bugs.kde.org/show_bug.cgi?id=483060
Daniel Vrátil changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=483060
Thiago Macieira changed:
What|Removed |Added
CC||ch.ehrlic...@gmx.de
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=483060
--- Comment #7 from Joshua J. Kugler ---
(In reply to Christophe Marin from comment #2)
> Duplicate of 483061?
That's quite funny. Mine is even the very next bug filed after this one. :)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=483060
--- Comment #6 from Joshua J. Kugler ---
When I was debugging this, someone in the #maria IRC channel said:
> As a workaround SQL mode flag ALLOW_INVALID_DATES should help, but it is
> better to store the UTC values properply as UTC.
So, there is
https://bugs.kde.org/show_bug.cgi?id=483060
Thiago Macieira changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=483060
Thiago Macieira changed:
What|Removed |Added
CC||jos...@joshuakugler.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=483060
--- Comment #3 from Thiago Macieira ---
(In reply to Christophe Marin from comment #2)
> Duplicate of 483061?
Looks like two people experienced the same problem at around the same time,
yes.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=483060
--- Comment #2 from Christophe Marin ---
Duplicate of 483061?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=483060
--- Comment #1 from Thiago Macieira ---
Or use the SET GLOBAL time_zone command.
--
You are receiving this mail because:
You are watching all bug changes.
