[CONJ-286] Deploying non-JDBC-compliant driver Created: 2016-04-22  Updated: 2016-04-25  Resolved: 2016-04-25

Status: Closed
Project: MariaDB Connector/J
Component/s: Other
Affects Version/s: 1.4.3
Fix Version/s: 1.4.3

Type: Bug Priority: Minor
Reporter: Christian Bourque Assignee: Diego Dupin
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

WildFly 8.2.1 (Java 7)


 Description   

We use the MariaDB connector on WildFly 8.2.1 and during the startup process I see this message on the console and I was wondering why it would report that:

2016-04-22 10:42:46,075 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010404: Deploying non-JDBC-compliant driver class org.mariadb.jdbc.Driver (version 1.4)

Is it true that the current version of the driver is not 100% JDBC compliant?

 Comments   
Comment by Diego Dupin [ 2016-04-25 ]

driver is jdbc 1.4.0 compliant, but not completely support 1.4.1, 1.4.2.
I'm checking why that is happening.

Comment by Diego Dupin [ 2016-04-25 ]

Jboss use Driver.jdbcCompliant() ( https://docs.oracle.com/javase/7/docs/api/java/sql/Driver.html#jdbcCompliant() ) to display this message.
This means driver is JDBC compliant AND database support SQL 92 Entry Level compliance.
Driver is JDBC 1.4.0 compliant, but since MariaDB cannot claim to be fully SQL 92 compliant, we cannot set this jdbcCompliant flag to true.

Comment by Christian Bourque [ 2016-04-25 ]

Ok I guess you can close this ticket! Thanks for looking at it

Generated at Thu Feb 08 03:14:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.