https://bugs.freedesktop.org/show_bug.cgi?id=59200
Lionel Elie Mamane <lio...@mamane.lu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ODBC - incorrect display |ODBC - incorrect display
|with mysql NULL timestamp |with mysql zero timestamp
|values using Actual |values using Actual
|Technologies ODBC driver |Technologies ODBC driver
--- Comment #4 from Lionel Elie Mamane <lio...@mamane.lu> ---
In MySQL, "0000-00-00 00:00:00" is not a NULL value, but a zero timestamp. NULL
and "0000-00-00 00:00:00" are distinct values. "0000-00-00 00:00:00" is a
MySQL-specific idiosyncrasy, an "anomalous" value which does *not* conform to
(from memory) the SQL standard, nor ODBC:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms712480(v=vs.85).aspx
and entries "SQL_TYPE_DATE/TIME/TIMESTAMP" in
http://msdn.microsoft.com/en-us/library/windows/desktop/ms710150(v=vs.85).aspx
The MySQL ODBC Connector (the driver provided by MySQL) has an option "convert
zero date/timestamp to NULL" so as not to leak these anomalous values to ODBC
applications; if the column is "NOT NULL", then it may confuse applications in
other ways :-| I haven't tested how LibreOffice reacts to this (NULL in a
non-NULLable column).
This being said, if we can change something in LibreOffice so that it reacts
more gracefully to such anomalous values, then it would be good, so let's keep
this bug open to track this future improvement.
To use applications that are not specifically designed for MySQL (such as
LibreOffice...), I'd recommend running MySQL with NO_ZERO_DATE and
NO_ZERO_IN_DATE options activated.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
