<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Collabora Office crashes when attempting to load database tables via the mysql native connector" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138946#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Collabora Office crashes when attempting to load database tables via the mysql native connector" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138946">bug 138946</a> from <a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> Alex Thurgood</a> <pre>(In reply to Tor Lillqvist from <a href="show_bug.cgi?id=138946#c5">comment #5</a>) > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>