On 01/19/2013 03:43 AM, Robert Großkopf wrote:
Hello Dan,

I have reported
https://bugs.freedesktop.org/show_bug.cgi?id=59481
(FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't
work any more with LO 4.0)
and
https://bugs.freedesktop.org/show_bug.cgi?id=59516
(FILEOPEN: Native MySQL-connector couldnt be installed under Windows in
LO 4.0)
        I looked through the bugs reports for possible duplication. I
found 59481 (Linux 32 bit RPM) which is this one,
59533 (Windows 32 bit), and 59516 (Windows 32 bit). All of them have the
same problem: the MySQL native connector can not be used to connect to a
MySQL data source. I use Ubuntu 12.04 LTS 32 bit, and I have the same
problem with the MySQL native connector. My conclusion is that the 32
bit version of it has a regressive bug. I can use this connector with LO
3.5.7.2 and 3.6.4.3 but not 4.0.0.1RC.
       Being new at this, should I change Platform to "All" for 59481?
Should 59533 and 59516 be marked as duplicates? Should I mark 59481 as
confirmed? I believe that these are the things that need to be done.
There is a difference in the behavior under Linux and Windows. The old
connector 1.0.1 doesn't work under Linux since 3.5. So you could only
connect with the 1.1.0 of AOO. Under Linux this connector could be
installed in LO 4.0.0.1 rc. Under Windows the installation fails.
Linux-user might think: Connector is installed, no error appears, should
work - but it doesn't: "... No SDBC driver was found for the given URL."
OK, I understand. Perhaps this points to a possible bug in the Extension Manager itself. The AOO version of this connector seems to install, but it fails to enable the connector. I have clicked the connector, and two buttons appear: Enable and Delete. When I click the Enable button, I get the error message. Seems to me that installing an extension should also enable it. Then if someone wants to disable an extension, he can open the Extension Manager to do this. This might be a bug, or is it a feature request?

--Dan
First I thought it was the same problem at Windows, but it wasn't (I
have no Window here at all, so it is reported from other persons by mail
to me). So I have to report another bug. See
https://bugs.freedesktop.org/show_bug.cgi?id=59481#c1

Only one bug in one report I have often heard. So I linked this two
reports with "See also ..."

Bug 59533 is a duplicate of 59516. Don't know, why the reporter is
writing a new bug. He always noticed bug 59481 and then he could also
notice the link to bug 59516. I will mark this report as a duplicate.

Regards

Robert
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Reply via email to