Bug 75853 - EDITING: Wrong timestamp in a table with date and time (except 00:00:00) before 1899-12-30
Summary: EDITING: Wrong timestamp in a table with date and time (except 00:00:00) befo...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Database-Queries
  Show dependency treegraph
 
Reported: 2014-03-06 21:06 UTC by Robert Großkopf
Modified: 2025-04-13 03:11 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Open the query and try to put 29.12.1899 10:00:00 in the timestampfield ... (4.30 KB, application/vnd.oasis.opendocument.base)
2014-03-06 21:06 UTC, Robert Großkopf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Großkopf 2014-03-06 21:06:29 UTC
Created attachment 95245 [details]
Open the query and try to put 29.12.1899 10:00:00 in the timestampfield ...

Open the attached database.
Open the query. Shows a date and a timestamp-field.
Put a date in the the timestamp-field (like 29.12.1899).
Works right.
Pute a full timestamp in the timestamp-field (like 29.12.1899 01:00:00)
Fails. The timestamp is saved as 30.12.1899 23:59:59.

Could be this is a special bug of HSQLDB. When I try the same with internal firebird I get other errors with all values before 1.1.1900 together with a time ...

I have tested it with many versions. It first appears in LO 3.3.0_Beta1 here. So I set the first version to "Inherited ..."
My System: OpenSUSE 12.3 64bit rpm Linux
Comment 1 Buovjaga 2014-11-08 14:42:25 UTC
I confirm. 29.12.1899 01:00:00 was saved as 31.12.1899 00:00:00

Win 7 64-bit Version: 4.4.0.0.alpha2+
Build ID: c989f5e0e11e295b11ffc921b0d105869e037e47
TinderBox: Win-x86@42, Branch:master, Time: 2014-11-07_22:50:48
Comment 2 Alex Thurgood 2015-01-03 17:39:43 UTC Comment hidden (no-value)
Comment 3 QA Administrators 2016-01-17 20:05:32 UTC Comment hidden (obsolete)
Comment 4 Alex Thurgood 2016-01-19 13:08:17 UTC
Still present in

Version: 5.0.3.2
Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75
Locale : fr-FR (fr.UTF-8)

OSX 10.11.2
Comment 5 QA Administrators 2017-03-06 14:44:14 UTC Comment hidden (obsolete)
Comment 6 Robert Großkopf 2017-03-06 20:03:58 UTC
Bug still exists with LO 5.3.1.1, OpenSUSE 42.1 Leap, 64bit rpm Linux.
Comment 7 QA Administrators 2018-03-07 03:40:48 UTC Comment hidden (obsolete)
Comment 8 Robert Großkopf 2018-03-07 17:57:51 UTC
Bug still exists with LO 6.0.2.1, OpenSUSE 42.3 Leap, 64bit rpm Linux.
Comment 9 QA Administrators 2019-03-08 03:39:41 UTC Comment hidden (obsolete)
Comment 10 Robert Großkopf 2019-03-08 15:52:19 UTC
Same buggy behaviour with LO 6.1.5.2 on OpenSUSE 15 64bit rpm Linux.
Comment 11 QA Administrators 2021-04-12 03:31:58 UTC Comment hidden (obsolete)
Comment 12 Robert Großkopf 2021-04-12 05:31:34 UTC
Bug still exists with LO 7.1.2.2 on OpenSUSE 15.2 64bit rpm Linux
Comment 13 QA Administrators 2023-04-13 03:23:50 UTC Comment hidden (obsolete)
Comment 14 Robert Großkopf 2023-04-13 06:02:21 UTC
Bug still exists with LO 7.5.2.2 on OpenSUSE 15.4 64bit rpm Linux
Comment 15 QA Administrators 2025-04-13 03:11:48 UTC
Dear Robert Großkopf,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug