| Summary: | VIEWING REPORTBUILDER: TIMESTAMP incorrectly displayed, (2 days behind) | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | jason |
| Component: | Database | Assignee: | Lionel Elie Mamane <lionel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | lionel, robert |
| Version: | 4.0.3.3 release | Keywords: | regression |
| Hardware: | x86-64 (AMD64) | ||
| OS: | All | ||
| See Also: |
https://bugs.freedesktop.org/show_bug.cgi?id=58805 https://bugs.freedesktop.org/show_bug.cgi?id=36858 https://bugs.freedesktop.org/show_bug.cgi?id=65354 https://bugs.freedesktop.org/show_bug.cgi?id=69873 |
||
| Whiteboard: | target:4.2.0 target:4.1.1 target:4.0.5 | ||
| i915 platform: | i915 features: | ||
|
Description
jason
2013-07-22 18:47:41 UTC
I cannot supply a testcase as it (almost certainly, but untested) requires an external MySQL database. It may fail with other external databases as well. In case you didn't catch it I am using a TIMESTAMP field, which automatically updates to the current date/time upon record change in my MySQL database. I require this feature to record when a particularly important record is changed. I can confirm this behavior. Have tested with LO 4.0.2.2 and MariaDB - direct connection and JDBC - works both fine. Dates are correct in Timestamp and DateTime-fields in a report. Same procedure with LO 4.0.3.3 and the shown dates in the report-builder are 2 days behind. I have added Lionel. See https://bugs.freedesktop.org/show_bug.cgi?id=58805#c29 Lionel Elie Mamane committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=cab9b82fb31217223511afcea88ad7446999492b fdo#67186 switch reporbuilder to null date == 1899-12-30 The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. backport to 4.0.4 and 4.1.1 requested at https://gerrit.libreoffice.org/5055 https://gerrit.libreoffice.org/5054 Lionel Elie Mamane committed a patch related to this issue. It has been pushed to "libreoffice-4-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=be945e8e54a93921a12597c7b3a5b012951600ac&h=libreoffice-4-1 fdo#67186 switch reporbuilder to null date == 1899-12-30 It will be available in LibreOffice 4.1.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Lionel Elie Mamane committed a patch related to this issue. It has been pushed to "libreoffice-4-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ac2d93cca0791a728583a40dc379c89c22582855&h=libreoffice-4-0 fdo#67186 switch reporbuilder to null date == 1899-12-30 It will be available in LibreOffice 4.0.5. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Lionel Elie Mamane committed a patch related to this issue. It has been pushed to "libreoffice-4-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6bd204f6355b15632e6a9e94fd03faab769fdadd&h=libreoffice-4-0 fixup cherry-pick of fdo#67186 fix It will be available in LibreOffice 4.0.5. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.