[jira] [Commented] (JENA-1192) Support the MariaDB JDBC driver

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324399#comment-15324399 ] 

ASF subversion and git services commented on JENA-1192:
-------------------------------------------------------

Commit edba13136e2dd201e26e24a62e3f1b8a5c20e81e in jena's branch refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=edba131 ]

JENA-1192: Support for the MariaDB JDBC driver.


> Support the MariaDB JDBC driver
> -------------------------------
>
>                 Key: JENA-1192
>                 URL: https://issues.apache.org/jira/browse/JENA-1192
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: SDB
>    Affects Versions: Jena 3.1.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>
> The MariaDB JDBC is compatible with the MySQL JDBC driver. It has different license; the MariaDb JDBC driver is LGPL and the MySQL JDBC driver is GPL with a special FOSS exception.
> In addition, the MariaDB JDBC driver response to "jdbc:mysql:..." URLs.
> Supporting the driver has two parts: 
> When MariaDB is explicitly chosen in "sdb:sdbType", we have a registration for  "MariaDB" to map to "org.mariadb.jdbc.Driver" and ideally build the right JDBC URL for the case when the URL is not explicitly provided.
> The other part is for a setup is for MySQL but only the MariaDB JDBC driver is on the classpath. We can treat this as a special-case during the loading of the JDBC driver so if looking for the MySQL classname ""com.mysql.jdbc.Driver" fails, the code also looks for "org.mariadb.jdbc.Driver".
> At no point is Jena (source or binary) shipping either JDBC driver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)