https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #26 from t...@tim-passingham.co.uk ---
My understanding is that this is all to do with Mysql(Native) connections and
the version of software used. I have resigned myself to using ubuntu ppa
releases so as to get compatible connectors,
https://bugs.freedesktop.org/show_bug.cgi?id=66763
Lionel Elie Mamane changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #24 from rob...@familiegrosskopf.de ---
(In reply to comment #23)
> @robert (comment 21): Please add your experience with the crashing extension
> on openSUSE to the bug report, which I have created, so that it gets more
> usefull info
https://bugs.freedesktop.org/show_bug.cgi?id=66763
Dennis Grunert changed:
What|Removed |Added
CC||dennisgrun...@hotmail.de
--- Comment #2
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #22 from Alex Thurgood ---
So, should we set this to WFM, as it is yet again the age old problem of
finding the correct coupling of LO version and connector version.
Alex
--
You are receiving this mail because:
You are the assigne
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #21 from rob...@familiegrosskopf.de ---
I have tested it with ODBC and JDBC on OpenSUSE 12.3 64bit with a MariaDB. The
time, the dates and the timestamps are shown well and you could also input new
time etc.
The extension for MySQL co
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #20 from t...@tim-passingham.co.uk ---
I am now on 4.1 on my ubuntu 64 bit system, installed from the ubuntu ppa. This
includes a native connector which, I assume has been compiled for 4.1.
The dates are correct.
On my debian 32 bit
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #19 from t...@tim-passingham.co.uk ---
I have run 4.1.0.3 RC on a 32 bit Linux Debian system using JDBC. I can't say
I have done exhaustive tests, but the date/times I have stored already display
OK in both JDBC and the same fields a
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #18 from Fernand ---
Can someone confirm that there is no date time problems using JDBC or ODBC with
versions 4.1
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #17 from t...@tim-passingham.co.uk ---
For what Alex has written I can see that the connector is a problem, and that
it may not be possible to provide a stable fix.
Should someone put a health warning against the connector extension a
https://bugs.freedesktop.org/show_bug.cgi?id=66763
rob...@familiegrosskopf.de changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #15 from rob...@familiegrosskopf.de ---
One hint for working MySQL-connectors and working MariaDB-connectors, tested
under LO 4.0.*, 4.1 rc and 4.2beta Linux 64bit rpm:
http://code.google.com/a/apache-extras.org/p/aoo-my-sdbc/
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #14 from Fernand ---
Alex,
The latest Windows version was compiled against 4.0 and is still working for
4.1 but there are some issues but it is not sure if this issues are due to the
connector or due to the recent changes in the bas
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #13 from t...@tim-passingham.co.uk ---
Alex - Thanks very much for that.
>From what you say my conclusion is that MySql(Native) connector is effectively
ruled out for anyone trying to use LO 4.anything-at-all unless their OS distro
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #12 from Alex Thurgood ---
(In reply to comment #9)
> must confirm same behaviuour sinde 4.1 for windows and the windows native
> connector
> changing tdatetime using a statement go wrong as wel
Fernand, against which source version
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #11 from Alex Thurgood ---
(In reply to comment #10)
> I have tried, but failed thus far, to install a version 1.0.2
> libreoffice-mysql-connector from packages.debian.org/sid. I am getting
> dependencies that I can't satisfy (for i
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #10 from t...@tim-passingham.co.uk ---
I have tried, but failed thus far, to install a version 1.0.2
libreoffice-mysql-connector from packages.debian.org/sid. I am getting
dependencies that I can't satisfy (for instance libc6_2.17-7_
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #8 from t...@tim-passingham.co.uk ---
I entered the GBP date as 10/7/2013 using MySql(Native). If I read it using
MySql(Native) it displays correctly. If I read it directly from MySql using a
dump it is incorrect.
I entered the USD
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #9 from Fernand ---
must confirm same behaviuour sinde 4.1 for windows and the windows native
connector
changing tdatetime using a statement go wrong as wel
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #7 from Alex Thurgood ---
Oh and of course "0007-10-00" is an invalid date in real life, but mysql
doesn't seem to care :
http://dev.mysql.com/doc/refman/5.0/en/datetime.html
"For the DATE and DATETIME range descriptions, “supported
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #6 from Alex Thurgood ---
Comparative date string entries :
mysql> select * from AC;
+-+--+-+-+
| bid | Ac | Cur | dt |
+-+--+-+-+
| 1 | AC1 | GBP
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #5 from Alex Thurgood ---
Even when using JDBC, I don't see any difference on 4.2.0.0alpha. After
entering some more dates via JDBC, here's what I see when looking at the table
from the console :
mysql> select * from AC;
+-+-
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #4 from t...@tim-passingham.co.uk ---
I may not have explained the issue clearly enough.
The GBP date was created when the odb was connected using the MySql(Native)
connector.
The USD Date was created when the odb was created using t
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #3 from Alex Thurgood ---
Hi Tim,
The first line shows up as 02/10/7 for me in the test table I created from your
SQL.
The second line shows the date correctly. Only if I enter an invalid date, do I
get an erroneous display.
Teste
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #2 from t...@tim-passingham.co.uk ---
Created attachment 82280
--> https://bugs.freedesktop.org/attachment.cgi?id=82280&action=edit
Date Test odb
See previous comment. Look at table AC.
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=66763
--- Comment #1 from t...@tim-passingham.co.uk ---
Created attachment 82279
--> https://bugs.freedesktop.org/attachment.cgi?id=82279&action=edit
Test database
This MySql database, when accessed from my test odb (in the next post) has
dates in ta
https://bugs.freedesktop.org/show_bug.cgi?id=66763
t...@tim-passingham.co.uk changed:
What|Removed |Added
CC||t...@tim-passingham.co.uk
27 matches
Mail list logo
