https://bugs.documentfoundation.org/show_bug.cgi?id=93849
Bug ID: 93849
Summary: Allow specifying the JDBC jar in the Database Wizard
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: medium
Component: Base
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
In the context of <https://bugzilla.redhat.com/show_bug.cgi?id=1258913> "The
driver class 'com.mysql.jdbc.Driver' could not be loaded" I asked Lionel:
"With whatever LO version I try, it appears to always be the case that 'File -
New - Database - Connect to an existing database: MySQL - Next >> - Connect
using JDBC (Java Database Connectivity) - Next >>', keep default 'MySQL JDBC
driver class: com.mysql.jdbc.Driver', then 'Test Class' leads to 'The JDBC
driver could not be loaded' [...]. Is that expected, and users expected to
manually add a jar to LO's JVM class-path settings, or what am I missing?"
To which he responded:
"The wizard text says 'a JDBC driver class must be installed on your system and
registered with LibreOffice'. I can understand 'registered with LibreOffice' as
'added to the JVM class-path setting'. So it seems the system is currently
designed like that, yes.
"Can we improve on that?
"One first (and I think already great step forward UI/HI-wise) would be that
the wizard, in the same page where it asks for the driver class, asks for the
path to the jar file. This is valid not only for MySQL-JDBC, but for any JDBC
connection: generic JDBC, Oracle JDBC.
"To go further than that:
"In the context of a GNU/Linux distribution (or *BSD port collection), the
packager knows where the system puts the packaged MySQL JDBC driver (e.g.
/usr/share/java/mysql.jar and /usr/share/java/mysql-connector-java.jar on
Debian), so we could at least look up there automagically. But the user should
be able to override that to use another jar. At the upstream (LibreOffice)
level, we could make that an option of ./configure (e.g. some better name
than --with-mysql-jdbc-jar-runtime-path). What it would be set to in our TDF
builds is a good question... Maybe instead of a single path, a list of paths,
corresponding to the main GNU/Linux distributions and also where the
tarballs/packages downloaded directly from
https://downloads.mariadb.org/connector-java/
http://dev.mysql.com/downloads/repo/yum/
http://dev.mysql.com/downloads/repo/apt/
http://dev.mysql.com/downloads/repo/suse/
http://dev.mysql.com/downloads/connector/j/
install to.
"On Microsoft Windows, we could look up in the default install path of the
MySQL Java connector and of the MariaDB Java Connector (if they differ).
"I suppose a similar thing can happen on MacOS X."
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
