| Summary: | Collabora Office crashes when attempting to load database tables via the mysql native connector | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Alex Thurgood <iplaw67> |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED NOTABUG | ||
| Severity: | major | CC: | aron.budea, tml |
| Priority: | high | ||
| Version: | 6.4.7.2 release | ||
| Hardware: | ARM | ||
| OS: | macOS (All) | ||
| See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=138949 https://bugs.documentfoundation.org/show_bug.cgi?id=138989 |
||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
|
Description
Alex Thurgood
2020-12-15 16:20:57 UTC
How do I set up a mysql instance to connect to? I don't even know if that means just a database consisting of local files used by code inside LibreOffice (or in this case, Collabora Office), or a server on some other (possibly Linux) machine perhaps. I need much more detailed reproduction instructions... http://sheepdogguides.com/srv/s0MySqlFrmBase.htm should get you on your way to creating an ODB file that connects to a mysql server database, using the native mysql connector. Alternatively, there is the Base Guide : https://nextcloud.documentfoundation.org/s/Rt67sEsWtg4TQJR in particular pages 58-62 OK, I managed to create a MariaDB server on my Fedora box, and could connect to it using TDF LibreOffice on macOS on x86_64. But now I realise that Collabora Office and LibreOffice Vanilla in the App Store are built without the MariaDB Connector code. That is not new, and on purpose because they use only the MPL subset of the code. So this probably could be closed as NOTABUG? (In reply to Tor Lillqvist from comment #3) > OK, I managed to create a MariaDB server on my Fedora box, and could connect > to it using TDF LibreOffice on macOS on x86_64. But now I realise that > Collabora Office and LibreOffice Vanilla in the App Store are built without > the MariaDB Connector code. > > That is not new, and on purpose because they use only the MPL subset of the > code. So this probably could be closed as NOTABUG? Ah that is very unfortunate, and thus puts and end to my adoption in the work environment of Collabora Office (and even LO Vanilla for that matter). Our database environment at work is MySQL/MariaDB. If we can't connect to that environment using the ODB files we have had and which have functioned for more than a decade, that is a naturally major issue. It probably would be a good idea to file a separate bug, for something like:
> Even with --disable-mariadb-sdbc, various menus and messages include the MySQLC alternative.
But first one would need to verify on Linux that that indeed is the case. Doing it now.
Also note that the help message for the --disable-mariadb-sdbc option apparently incorrrectly says "Disable the build of the MariaDB/MySQL-SDBC driver." even if what it actually means is "Disable the *use* (and build, if necessary) of the MariaDB/MySQL-SDBC driver".
s/MySQLC/MySQL (In reply to Tor Lillqvist from comment #5) > It probably would be a good idea to file a separate bug, for something like: > > > Even with --disable-mariadb-sdbc, various menus and messages include the MySQLC alternative. > > But first one would need to verify on Linux that that indeed is the case. > Doing it now. > > Also note that the help message for the --disable-mariadb-sdbc option > apparently incorrrectly says "Disable the build of the MariaDB/MySQL-SDBC > driver." even if what it actually means is "Disable the *use* (and build, if > necessary) of the MariaDB/MySQL-SDBC driver". You read my mind...:-) There is zero point in having all of the UI connection dialogs, wizard bits, etc that point to mysql/mariadb support if you can't include the code in your release We could have the same discussion about the Advanced dialog under Preferences wrt Java. Idem wrt ODBC support (which is also non-existent in Collabora Office) I'll open separate bug reports for those two. |