Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Thanks for the prompt answer! By the way, I am using the  Linux .deb-Version
of LO. This is NOT a show stopper for me. I will continue to use the Java-
connector until this problem is fixed...
Regards
H.S.

On Tue, 29 Oct 2013 09:20:18 +0100, Fernand Vanrie <sos@pmgroup.be> wrote:

Heinrich ,

Lionel is working on it he changed the internal MariaDB code back to the
MySQL code i am not sure if this changes go's into the version you uses
?, on Windows we have the same situation, when using ODBC no date
problems and Jésús is working on a new Windows compile.
Greetz


Hello,
I just downloaded pre-release LO 4.1.3.2. It includes a native MySQL
connector.
However, the same as in previous LO 4.1.x "shipments", time values are
still
handled incorrectly. What I see is that - for a time value of
"20:00:00" - the
column is shown as "12:20:00" for example. ALL time values are shown
this way.
When accessing the database through JDBC everything is o.k.
Regards
H.S.




--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/

--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.