Apache OpenOffice (AOO) Bugzilla – Issue 66158
Address Datasource, MySQL, JDBC and F4 crashes
Last modified: 2013-08-07 15:45:17 UTC
Hi all, Things aren't going well for me with my database access under MacOSX 10.3.9 and OOo2.03.rc5 French. Mysql : remote 4.1.12 JDBC : latest driver provided by MySQL I have used the Address Source wizard to assign a table from a mysql database. The wizard suggests using "Adresses" as the name for the database ODB document, but I already have one ODB document declared that accesses the same database, so I chose the existing ODB document and confirmed the overwrite question when asked, but keep the suggested datasource name entry, i.e. "Adresses. Just to make things clear : I now have an ODB called "Cabinet" containing a reference to my address table, declared in OOo as "Adresses". Now when I press F4 I see a new entry in the list of datasources "Adresses" as should be. I am automatically asked for the user id and password, I enter the required id/pwd combo and then the list of tables starts to be displayed. Before OOo can finish displaying the tables, it crashes without any error message. I have tried restarting OOo and pressing F4 once the blank Writer document is displayed. The same crash happens. Steps to reproduce : 1) Define a datasource for the Addresses within OOo. Follow the wizard through and make the fields correspond. Save the file as an ODB. 2) Now press F4. A password dialog appears for access to the mysql db. Enter user id/pwd combo and press OK 3) The DSB pane starts to attempt to display the list of tables in the db and the corresponding table that has previously been chosen by the wizard as the address db. Then it crashes before it has a chance to finish displaying either the selected table or any of its data. Reprocudicble 100%. Alex
setting oooqa, crash keywords setting priority to P1
(generally it works fine in a 680m171 => seems to be a mac only bug) clu->jogi: like we have spoken, please check if you can, and/or send further to corresponding person from mac project thx
Hi all, Problem still present in rc6 :-( Alex
please don't file P2 issues as P1
@ja : The problem is still present in rc7. For me this is P1, it affects basic operation of the application. If I hit F4, OOo crashes - repeatable 100%. I would be interested to hear why you thin it shouldn't be P1. The guidelines don't seem to make that very clear, apart from stating that this should be exceptional. Well, like it or not, I'm afraid, IMHO it is. Alex
macjogi->reporter: 1. Always submit the driver package you are using: "Beta 5.0.3" or "Generally Available (GA) 3.1.13" 2. Enter the steps you have done to connect the database (stepwise) 3. mySQL is an external database and never a P1 if the connection could not be established. This is the only chance I see to get the issue reproduced on my machine.
Hi, For the environment specifics, look at Issue 66123, this issue is linked to that one IMHO, and I shall link this issue to it as a dependency. You may want to correct me if you disagree. Alex
including dependency and linked issue alex
@wurzel: What is the difference between this issue and issue 66123? I don't see any and am closing this issue as a duplicate to 66123. James M. *** This issue has been marked as a duplicate of 66123 ***
@james The difference here is that 66123 dealt with Mailmerge to a remote mysql db via a JDBC connector. This issue dealt with what happened if you defined the default Address database as a remote mysql db using a JDBC bridge. It was not obvious from the beginning that the two were linked. However, further testing with rc7 has led me to believe that the whole JDBC connectivity thing is non-functional with a remote mysql database. I have now tried various combinations of drivers, and two different versions of OOo MacOSX PPC, and any of these combinations leads to a crash in OOo when the user chooses a table, no matter which way that table is chosen, from the list of tables presented to him when he connects to the remote mysql db. So in a sense, I agree with you that this is in effect a duplicate, although I didn't wish to describe two different use cases that led to crashes without being certain that they were linked to one and the same problem. I just didn't want this issue to get lost at sea, so to speak. The bottom line of the matter is : you can not open a table from a remote mysql db using a mysql JDBC connector without causing the MacOSX PPC version of OOo to crash. Thanks for looking into this, Alex
closing