Incorrect handling of time values in O 4.1.1

users
#1

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. Please look at
bugzilla, bug No. 69116. I am running LO under Debian-Wheezy, 32-bit. Anybody with
the same problem?
Regards
H.S.

#2

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

#3

Bon Soir, Fernand,
I connect to the database using the native MySQL connector.
Regards
H.S.

#4

Heinrich ,

btw its Flemish (like Dutch) :slight_smile:

Bon Soir, Fernand,
I connect to the database using the native MySQL connector.

the connector must at least been recompiled against the 4.1 code maybe , just maybe the the dattime problems sould been gone.
I am waiting for a recompiled windows connector to do further tests

#5

Hello Fernand,
excuse - I thought it was francais (wallon)...
I just downloaded the latest MySQL Native Connector. It has in fact been
compiled only for 4.0. Since the treatment of date/time values has
apparently changed in 4.1, this might be the cause - as you suggest.
In any case, can anybody shed light on this?
Regards
H. S.

#6

Hi Heinrich, Fernand,

excuse - I thought it was francais (wallon)...
I just downloaded the latest MySQL Native Connector. It has in fact been
compiled only for 4.0. Since the treatment of date/time values has
apparently changed in 4.1, this might be the cause - as you suggest.
In any case, can anybody shed light on this?
Regards

Known bug, previously discussed here on this list or in one of the BZ
reports :

https://bugs.freedesktop.org/show_bug.cgi?id=66763

Linked to the fact that the mysql connector needs to be recompiled for
4.1 and made available outside of the Linux distros, for Mac and for
Windows, as far as I can recall.

Alex