Bon Soir, Fernand,
I connect to the database using the native MySQL connector.
Regards
H.S.
On Mon, 09 Sep 2013 19:30:24 +0200, Fernand Vanrie <sos@pmgroup.be> wrote:
Heinrich ,
same sort of problems with Windows, datetime values are scrambled sinds 4.1
it is still not defined if this problem is comming from the MySQL
Connector or its due to ????
how do you connect to your MySQL server ?
Hello,
I have just filed a bug report regarding erroneous handling of
MySQL-time values
in LO 4.1.1. It happens both when entering data into a table through
Base as well
as later on looking at tables/views. This is QUITE serious in my view.
On top of
that, report builder doesn't run when time values occur in a report.
Date values
are actually han116dled correctly. The same report executed quite o.k.
under 3.6.7.
This certainly blocks me from going to 4.1 for production purposes.
+1
Please look at
bugzilla, bug No. 69116. I am running LO under Debian-Wheezy, 32-bit.
Anybody with
the same problem?
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.