[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 Lionel Elie Mamane lio...@mamane.lu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #25 from Lionel Elie Mamane lio...@mamane.lu --- Cannot reproduce with my 4.1 dev tree, so assuming fixed somewhere between 4.1.0 and 4.1.4. I mean, the corrupted values are still corrupted in the database, but when my dev tree inserts / modifies a timestamp value, it is correct in the database. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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, or using Mysql(JDB) otherwise. Are you saying there is now a better mysql connector out there? I see no updates in the extension library. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 Dennis Grunert dennisgrun...@hotmail.de changed: What|Removed |Added CC||dennisgrun...@hotmail.de --- Comment #23 from Dennis Grunert dennisgrun...@hotmail.de --- @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 information for the openSUSE devs: https://bugzilla.novell.com/show_bug.cgi?id=829430 -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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 information for the openSUSE devs: https://bugzilla.novell.com/show_bug.cgi?id=829430 I have reported a bug for OpenSUSE: https://bugzilla.novell.com/show_bug.cgi?id=834390 For LO 4.0.* the AOO-connector should work, because there has nothing be changed for date and time, see comment15 . -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #22 from Alex Thurgood ipla...@yahoo.co.uk --- 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 assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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 could not work in 4.1, because there had been something changed with the time in the API. When I had a look at the extension-site I could see, that there are extensions for 4.0, but not for 4.1. But I could also see titles like Connector for 4.*. The extension-site is a little bit confusing. Here is the 4.0-connector for Linux - unreleased: http://extensions.libreoffice.org/extension-center/mysql-native-connector/releases/1.0 And this is the path to the Windows-connector: http://extensions.libreoffice.org/extension-center/mysql-native-connector-for-libreoffice-4.x When I read the compatibility, this connector is only for 4.0 I don't know, if this bug is reported at the right place. There is no connector available for 4.1 in the extensions. There are only connectors for Linux-distributions, when you use the LO-version of this distributions. For openSUSE this connector don't work at all - LO crashes immediately when trying to connect. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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 linux mint debian system I can find no version of LO or the connector specifically compiled for it, so I still have to us JDBC, at least for now. This 'bug' report therefore really belongs more appropriately as an error against the extension from the extension website. It would also be useful to document the issue somewhere where people can find it should they have problems with getting compatible versions. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #18 from Fernand s...@pmg.be --- 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. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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 are OK on a separate system using LO 3.6 and MySql Native Connector. New date/times are also set correctly. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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 at http://extensions.libreoffice.org/extension-center/mysql-native-connector-for-libreoffice-4.x where it says it is compatible with 4.0.0 and later? The linux versions at http://extensions.libreoffice.org/extension-center/mysql-native-connector/releases/1.0 already state that they are not final versions. 'Tis a shame, but given that JDBC works, albeit slowly, I guess it isn't a priority. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 rob...@familiegrosskopf.de changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #16 from rob...@familiegrosskopf.de --- I have tried with the connector from https://bugs.freedesktop.org/show_bug.cgi?id=66763#c15 When I put data in a Timestamp-field or in a DateTime-field it doesn't work right with LO 4.1.0.2 rc and LO 4.2.0 alpha. The input isn't a valid DateTime or Timestamp-input. You couldn't read this tables any more, when you try to connect with JDBC to the MariaDB. The same connector works with LO 4.0.3.3 and with AOO 4 rc1 without any problems in this fields. The connector shows also the wrong data of an input from LO 4.1.0.2 rc I change this bug-report to New. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #14 from Fernand s...@pmg.be --- 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 base stuff for 4.1 The man who compiled for us is Jésus Corius, who is now working on his Thesis to finisch his studies. I hope he can again stapin half August to recompile against 4.1 Greetz Fernand -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #3 from Alex Thurgood ipla...@yahoo.co.uk --- 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. Tested on LO 4.2.0.0 alpha master build. Alex -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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 the MySql(JDBC) connection. To demonstrate and prove it you will probably have to connect both ways and set and display the dates yourself. The GBP date is not 10/7/13 according to MySQL, whereas the USD date is. I believe changes have been made to the date/time handling recently, and that there can be issues with the version of the Mysql (Native) Connector employed. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #5 from Alex Thurgood ipla...@yahoo.co.uk --- 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; +-+--+-+-+ | bid | Ac | Cur | dt | +-+--+-+-+ | 1 | AC1 | GBP | 0007-10-00 00:00:00 | | 2 | AC2 | USD | 2013-07-13 00:00:00 | | 3 | AC3 | GBP | 2013-07-14 00:00:00 | | 4 | AC4 | USD | 1899-12-30 00:00:00 | | 5 | AC5 | GBP | 2013-07-10 00:00:00 | | 6 | fre | USD | 2007-10-02 00:00:00 | | 7 | AC7 | GBP | 2007-10-02 00:00:00 | +-+--+-+-+ 7 rows in set (0.00 sec) The only erroneous date in the bunch is the one I deliberately put in wrong. Perhaps I am just misunderstanding the whole thing. Which strings exactly did you type (in the Table View mode) into your table ? I have been entering the date strings as -MM-DD per the required mysql format. However, even if I type it in say, European date format, DD/MM/, it still appears to work properly. Alex -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #6 from Alex Thurgood ipla...@yahoo.co.uk --- Comparative date string entries : mysql select * from AC; +-+--+-+-+ | bid | Ac | Cur | dt | +-+--+-+-+ | 1 | AC1 | GBP | 0007-10-00 00:00:00 | | 2 | AC2 | USD | 2013-07-13 00:00:00 | | 3 | AC3 | GBP | 2013-07-14 00:00:00 | | 4 | AC4 | USD | 1899-12-30 00:00:00 | | 5 | AC5 | GBP | 2013-07-10 00:00:00 | | 6 | fre | USD | 2007-10-02 00:00:00 | | 7 | AC7 | GBP | 2007-10-02 00:00:00 | | 8 | AC8 | USD | 2015-01-03 00:00:00 | == jdbc : entered as 2015-01-03 | 9 | AC9 | GBP | 2010-12-31 00:00:00 | == native : entered as 31/12/2010 +-+--+-+-+ Is there something I'm not doing like you do ? Alex -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #7 from Alex Thurgood ipla...@yahoo.co.uk --- 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” means that although earlier values might work, there is no guarantee. Alex -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #9 from Fernand s...@pmg.be --- 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. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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 date as 10/7/2013 using MySql(JDBC). It reads correctly using JDBC, and also direct from MySql using a dump. Using MySql(Native) it displays garbage. In your example how did you enter bid6 and 7? They look rather like bid1 to me, as if they are 2013 dates but invalid. Lionel did talk about versions of the native connector to me when I had a similar problem on my ubuntu 64 bit 12.04 platform using LO from the ubuntu ppa. Switching from using the extension as downloaded from the LO extension website to the libreoffice-mysql-connector listed in the libraries (using synaptic) fixed the problem there. However, on my Mint Debian 32 bit platform the only compatible connector I can find is version 1.0.3 from the LO extension website. Lionel claimed at the time that he was unaware that there was a 1.0.3, so maybe there is some incompatibility somewhere with library versions. The only libreoffice-mysql-connector shown with synaptic is version 1.0.1 for LO 3.5.4 and I can't install it without installing all of LO 3.5.4 which I do not want to do because having versions 3 and 4 installed causes other difficulties. If there is some other connector that I should have installed then I'll happily do so. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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_i386.deb refuses to install, but doesn't give a reason). I am therefore beginning to think that there could be more fundamental library dependencies that can't be satisfied on my debian system. If that's the case I'm stuck, since my ubuntu system is the one I use in anger and I have so far not found any LO 4 that works well enough for my Base applications. I am also puzzled as to why there is a separate connector (1.0.3) in the LO extension library. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #11 from Alex Thurgood ipla...@yahoo.co.uk --- (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 instance libc6_2.17-7_i386.deb refuses to install, but doesn't give a reason). I am also puzzled as to why there is a separate connector (1.0.3) in the LO extension library. The reason is complicated : - the mysql connector code uses a C wrapper with a C++ wrapper on top of the C wrapper - the C wrapper was GPL, the C++ wrapper LGPL - this prevented the connector extension from being built and bundled with LO as an integral part because of the licensing requirements of the GPL ; - historically, therefore, the connector was a separate extension, but also required libstdc, version xyz, and libmysqlclient version xyz, to be present on the system where it was being used, as far as I understand it ; - because it was a separate extension, it was built for Linux by the various distros, it was never built for Mac, nor Windows (but see belows) ; - when ABI compatibility got broken during LibreOffice4 development, the connector no longer needed libstdc, but still required libmysqlclient version xyz, and had to be built for that version of LO4 - the old connector extensions stopped working at this point (1.0.1 and 1.02) ; - for a while, I was releasing connector extensions for Linux on the extensions website for Linux and Mac OSX, which sometimes worked, and sometimes didn't, with various flavours of LO 3.x - because they were distrib specific, I pulled them off the extensions site and shut down the page I had created ; - Dan Lewis then started providing his own builds of the connector on the extensions site, but by this time, the internal build code in LO had switched to using libmariadb client libraries which are released under the LGPL ; - I don't know whether Dan's connectors (the 1.0.3 version) are built using the previous libmysql or the actual libmariadb. On Windows, no one was building anything until recently, that's where someone stepped in (Fernand Vanrie ?) and offered a build machine or finance for that purpose, but this was building against the 3.6 code source tree, as I understand it, and not against LO4 source, which in the meantime switched to using libmariadb. I hope the above gives a better overview of why the situation is as it is today. Basically: - if you have a Linux distrib and are using a distrib version of LO, push the distrib to provide the connector if it doesn't do so already ; - if you want to use a version of LO other than that provided by the distrib, you either have to build the connector yourself with the same source tree version of LO's code, or else find some kind soul to do that for you and provide the connector along with all the required files ; - if you have Mac OSX, you're up creek without a paddle, unless you build it yourself, etc, etc ; - if you have Windows, you're up creek without a paddle again, unless, etc ad nauseam. Wonderful isn't it ? Anyway, I digress from the main topic of the bug so I'll stop there. Alex -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 --- Comment #12 from Alex Thurgood ipla...@yahoo.co.uk --- (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 of LO is your Windows connector built ? 4.0 ? 4.1 ? Alex -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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 supplies it, or they are prepared to try and compile their own. It would seem to me that the extensions on the LO website might benefit from even greater health warnings than they currently do. From what Fernand reports it seems to me this issue is confirmed for some versions of the connector. I don't think I am going to attempt to compile the connector myself, since my linux knowledge is mostly limited to user-level. I have built a few items in the past, but with LO I wouldn't really know where to start. I shall switch my test system on Debian to JDBC for now. Slow, but at least it avoids this problem. -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
https://bugs.freedesktop.org/show_bug.cgi?id=66763 t...@tim-passingham.co.uk changed: What|Removed |Added CC||t...@tim-passingham.co.uk Summary|Date fields in Mysql being |Date fields in Mysql being |misenterpreted |misinterpreted -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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=82279action=edit Test database This MySql database, when accessed from my test odb (in the next post) has dates in table AC on a 32 bit Linux Mint Debian system running 4.1.0.2 RC2. The date against the entry bid 1 (GBP) was set up using MySql(Native). The date against the entry bid 2 (USD) was set up using MySql(JDBC). Both Dates were today (10/7/2013). The dates are self-conistent - JDBC can set and read dates it has set, and Native can do likewise. However JDBC can't understand the Native ones or vice-versa. When inspected using phpMyAdmin the date set using JDBC is correct. The other isn't. The date set using JDBC is also understood correctly on my other system running 3.6.6.2 MySql(Native). -- 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
[Libreoffice-bugs] [Bug 66763] Date fields in Mysql being misinterpreted
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=82280action=edit Date Test odb See previous comment. Look at table AC. -- 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
