https://bugs.documentfoundation.org/show_bug.cgi?id=157909
--- Comment #7 from Alex Thurgood <ipla...@tuta.io> --- (In reply to Petr Poruban from comment #6) > converted tables from the original Base internal database to MariaDB using > Calc, and it seems that empty fields were replaced with the form > "0000-00-00," which generates a minimum date of January 1, 1800 in the > cells. Whether this is a bug, you will have to assess. When I converted data > in the same way and used the Base ODBC connector to access MariaDB, the > fields remained empty. I dont chect at that time if the fields were > 0000-00-00 becouse there was no probem... Data Migration The now infamous Calc drag'n'drop / copy-paste to Base wizard is a well known culprit for screwing things up, unfortunately. The situation appears to have been compounded here because your NULL DATE fields seem to have been represented initially as "0000-00-00" when you copied the data into Calc. Calc's date converter unit converts "0000-00-00" to the default date from which all dates are counted, as defined under LibreOffice > Preferences > Calc > Calculations. So, when you copy data via Calc into a database table, the wizard takes the default zero date as the date to be inserted in the mariadb table. Not pretty, and probably should be considered a bug, IMHO. I have a vague recollection that this might already have been flagged up in another bug report, but would have to go looking for it. DATE DISPLAY IN A CONTROL (grid view, table data entry mode, etc) There could also be a separate bug in the display of the date in the grid control with regard to unfilled date values, leading to a default proposed display of 01/01/1900. Currently, there is already a bug report about Mariadb connections showing data from the previous tuple in a table grid view when entering a new tuple / resultset, but that displayed data isn't saved to the table. -- You are receiving this mail because: You are the assignee for the bug.
