If you want to use the native connection to MySQL you have to install the connector aoo-my-sdbc-1.1.0, when you use a version 3.4, 3.5 or 3.6. (http://extensions.openoffice.org/en/project/aoo-my-sdbc) When you update to 4.0 this connector didn't work any more. You could install the extension, but when you try to connect, the following popup appears: "... No SDBC driver was found for the given URL." Many users need a working direct connection, because this connection is the fastest and the best way to get many functions of MySQL working in Base.
For other systems (*.deb) there are other connectors, which could work. I have tested with OpenSuSE 32bit rpm. For Windows I have to submit another bug. The installation of the connector don't work with windows any more. See https://bugs.freedesktop.org/show_bug.cgi?id=59516
Is the extension still relevant now that LibreOffice has integrated support for MySQL?
Please ignore my comment 2. It was far too late in the day for me to know what I was typing. Terry.
Can't confirm at the moment, as my own built connector works with master. Alex
Don't get the same error on Pear Linux 5 (Ubuntu based 32bit), but it requires a id/password combo even though I don't need one to access my mysql test db and thus fails with an error message "id/password required" But I don't get the component loading error. Alex
tested on master build
oops, should've mentioned the build version : Version 4.1.0.0.alpha0+ (Build ID: 6880e2d31a38d5f4b44ba4f5b4a2b3e361a6631)
Using Version 4.0.0.0.beta2 (Build ID: 4104d660979c57e1160b5135634f732918460a0) on 32 bit Ubuntu 12.04 LTS. the native connector for MySQL does not work that I downloaded from the AOO extension. Error message: The connection to the data source "MySQL" could not be established ... No SDBC driver was found for the given URL. Using the same MySQL native connector, I can connect to my MySQL server using LO 3.5.7.2 and AOO 3.4.1. (32 bit Ubuntu 12.04 LTS)
(In reply to comment #8) > Using Version 4.0.0.0.beta2 (Build ID: > 4104d660979c57e1160b5135634f732918460a0) on 32 bit Ubuntu 12.04 LTS. the > native connector for MySQL does not work that I downloaded from the AOO > extension. Error message: The connection to the data source "MySQL" could > not be established ... No SDBC driver was found for the given URL. > Using the same MySQL native connector, I can connect to my MySQL server > using LO 3.5.7.2 and AOO 3.4.1. (32 bit Ubuntu 12.04 LTS) In all cases, I used the same database file to connect to my MySQL 5.5 server. Also, LO 3.6.4.3 will connect to MySQL.
(In reply to comment #4) > Can't confirm at the moment, as my own built connector works with master. > > Alex There is no other connector available for users of Linux-rpm-systems. When I try to install http://extensions.libreoffice.org/extension-center/mysql-native-connector-for-mac-osx/releases/1.0.1 the following popup appears: loading component library failed: file:///home/robby/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lumraylo.tmp_/mysql-connector-ooo.oxt/mysqlc.uno.so There is a difference between *.deb and *.rpm. While I have read https://bugs.freedesktop.org/show_bug.cgi?id=59481#c8 I will change the status to New.
(In reply to comment #10) Hi Robert, > There is no other connector available for users of Linux-rpm-systems. When I > try to install > http://extensions.libreoffice.org/extension-center/mysql-native-connector- > for-mac-osx/releases/1.0.1 I have asked for these connector extensions to be withdrawn and the pages deleted, since I have no intention of maintaining stuff for a moving target, so I wouldn't even consider them for testing. > > There is a difference between *.deb and *.rpm. Yes, of course, I'l well aware of that, but my home built connectors are not packaged according to one or another distribs packaging system, they come as raw OXT files. I'll post copies of my own 32bit and 64bit Linux connectors here. You can always try them out with your respective 32bit or 64bit OS to see if it makes a difference. My guess, from previous experience, is that it won't because the version numbers of the libraries/paths required to build the connectors on each different Linux OS might well vary such as to render my Ubuntu based ones useless on a system such as Suse, Arch, Fedora, etc. Alex
(In reply to comment #11) > > I'll post copies of my own 32bit and 64bit Linux connectors here. You can > always try them out with your respective 32bit or 64bit OS to see if it > makes a difference. My guess, from previous experience, is that it won't > because the version numbers of the libraries/paths required to build the > connectors on each different Linux OS might well vary such as to render my > Ubuntu based ones useless on a system such as Suse, Arch, Fedora, etc. > Ho hum, the OXT files are too big for bugzilla to handle...so no uploads here. Alex
32 bit Linux connector built against LO master : http://dl.dropbox.com/u/107086405/linuxmysqlconnector32bit/mysql-connector-ooo.oxt
64bit connector built against master http://dl.dropbox.com/u/107086405/linuxmysqlconnector64bit/mysql-connector-ooo.oxt
Adding Lionel and Julien to CC
i bet this is caused by lack of STLPort library, which is needed on 32-bit Linux and 32-bit Windows; if the extension still works on other platforms then that's the reason.
(In reply to comment #13) > 32 bit Linux connector built against LO master : > > http://dl.dropbox.com/u/107086405/linuxmysqlconnector32bit/mysql-connector- > ooo.oxt Hello Alex, just tested it. Could not install the extension. "loading component library failed: ..." This has been an old problem, not new in LO. Exists since 3.5 in OpenSuSE 32bit rpm. Only the connecter from AOO could be installed and worked.
So, it is probably linked to the changes in the service manager implementation and component registration code that were added during development for 3.7/4.0. Alex
(In reply to comment #16) > i bet this is caused by lack of STLPort library, which is needed > on 32-bit Linux and 32-bit Windows; if the extension still works > on other platforms then that's the reason. And sure enough, "readelf -d" on Linux_x86/libmysqlcppconn.so contained in <http://aoo-my-sdbc.apache-extras.org.codespot.com/files/aoo-my-sdbc-1.1.0-linux-x86.oxt> includes > 0x00000001 (NEEDED) Shared library: [libstlport_gcc.so] So this too is a consequence of removing support for STLport in legacy extensions for Linux x86 and Windows x86 from LO 4.0, see <http://lists.freedesktop.org/archives/libreoffice/2012-December/042804.html> "modules removal surprises."(In reply to comment #17) > (In reply to comment #13) > just tested it. Could not install the extension. "loading component library > failed: ..." > > This has been an old problem, not new in LO. Exists since 3.5 in OpenSuSE > 32bit rpm. Only the connecter from AOO could be installed and worked. Note that additional reasons why this might already not have work in versions of LO prior to 4.0 can be bug 59237 and the fact that at least some Linux distros reportedly already stopped to distribute the STLport library with older LO x86 versions.
@Stephan: so what would be the recommended solution to this problem ? Alex
you mean except "do not use a extension built for AOO" and "use the versions from comment 13 and comment 14"? That one's the solution. (Unless we want to re-ship stlport, which I don't think we should as we otherwise would do it for eternity). People using stuff on LO from some random - even for AOO unofficial aafair - place shouldn't wonder when that breaks somewhen ;)
(In reply to comment #21) Hi Rene, > you mean except "do not use a extension built for AOO" and "use the versions > from comment 13 and comment 14"? That one's the solution. (Unless we want to > re-ship stlport, which I don't think we should as we otherwise would do it > for eternity). The only problem with that is that the ones I provided in Comment 13 and 14 don't appear to work on anything other than Ubuntu-(Pangolin)-based distros, cf. Comment 17. Which brings us back to having to wait for the distros to update their builds and provide it for the various Linux flavours out there - ok, fair enough, no early QA pre-release testing then there. What about Windows ? What about OSX ? As far as I'm concerned, I can build my own connectors on Linux at the same time as I build LO from master (for the time being), so ultimately, I don't give a %%%%, but there are other QA'ers who can't build on their various OSes, for whatever reason (time, space, hardware, etc). Alex
(In reply to comment #22) > The only problem with that is that the ones I provided in Comment 13 and 14 > don't appear to work on anything other than Ubuntu-(Pangolin)-based distros, > cf. Comment 17. Note that Linux LO master builds are intended to be done on CentOS 5, so that is likely a good baseline to build any extensions (at least those involving C++) on, too.
AOO has changed the connector: http://code.google.com/a/apache-extras.org/p/aoo-my-sdbc/ Connection now works in LO 4.0, some problems in LO 4.1 (content of one table isn't shown, is another bug with timestamps ...) I will close this bug as worksforme.