How to check mysql connector j version

Here is some compatibility information for Connector/J 8.0:

  • JDBC versions: Connector/J 8.0 implements JDBC 4.2. While Connector/J 8.0 works with libraries of higher JDBC versions, it returns a SQLFeatureNotSupportedException for any calls of methods supported only by JDBC 4.3 and higher.

  • MySQL Server versions: Connector/J 8.0 supports MySQL 5.7 and 8.0.

  • JRE versions: Connector/J 8.0 supports JRE 8 or higher.

  • JDK Required for Compilation: JDK 8.0 or higher is required for compiling Connector/J 8.0. Also, a customized JSSE provider might be required to use some later TLS versions and cipher suites when connecting to MySQL servers. For example, because Oracle's Java 8 releases before 8u261 were shipped with JSSE implementations that support TLS up to version 1.2 only, you need a customized JSSE implementation to use TLSv1.3 on those Java 8 platforms. Oracle Java 8u261 and above do support TLSv1.3, so no customized JSSE implementation is needed.


Abstract

This manual describes how to install, configure, and develop database applications using MySQL Connector/J 8.0, a JDBC and X DevAPI driver for communicating with MySQL servers.

MySQL Connector/J 8.0 is highly recommended for use with MySQL Server 8.0 and 5.7. Please upgrade to MySQL Connector/J 8.0.

For notes detailing the changes in each release of Connector/J 8.0, see MySQL Connector/J 8.0 Release Notes.

For legal information, including licensing information, see the Preface and Legal Notices.

For help with using MySQL, please visit the MySQL Forums, where you can discuss your issues with other MySQL users.

Document generated on: 2022-09-02 (revision: 74063)

The Connector/J source code repository or packages that are shipped with source code include an extensive test suite, containing test cases that can be executed independently. The test cases are divided into the following categories:

  • Unit tests: They are methods located in packages aligning with the classes that they test.

  • Functional tests: Classes from the package testsuite.simple. Include test code for the main features of Connector/J.

  • Performance tests: Classes from the package testsuite.perf. Include test code to make measurements for the performance of Connector/J.

  • Regression tests: Classes from the package testsuite.regression. Includes code for testing bug and regression fixes.

  • X DevAPI and X Protocol tests: Classes from the package testsuite.x for testing X DevAPI and X Protocol functionality.

The bundled Ant build file contains targets like test, which can facilitate the process of running the Connector/J tests; see the target descriptions in the build file for details. To run the tests, in addition to fulfilling the requirements described in Section 4.3, “Installing from Source”, you must also set the following properties in the build.properties file or through the Ant -D options:

  • com.mysql.cj.testsuite.jvm: the JVM to be used for the tests. If the property is not set, the JVM supplied with com.mysql.cj.build.jdk will be used.

  • com.mysql.cj.testsuite.url: it specifies the JDBC URL for connection to a MySQL test server; see Section 6.2, “Connection URL Syntax”.

  • com.mysql.cj.testsuite.url.openssl: (for release 8.0.26 and earlier only) it specifies the JDBC URL for connection to a MySQL test server compiled with OpenSSL; see Section 6.2, “Connection URL Syntax”.

  • com.mysql.cj.testsuite.mysqlx.url: it specifies the X DevAPI URL for connection to a MySQL test server; see Section 6.2, “Connection URL Syntax”.

  • com.mysql.cj.testsuite.mysqlx.url.openssl: (for release 8.0.26 and earlier only) it specifies the X DevAPI URL for connection to a MySQL test server compiled with OpenSSL; see Section 6.2, “Connection URL Syntax”.

After setting these parameters, run the tests with Ant in the following ways:

  • Building the test target with ant test runs all test cases by default on a single server instance. If you want to run a particular test case, put the test's fully qualified class names in the com.mysql.cj.testsuite.test.class variable; for example:

    shell > ant -Dcom.mysql.cj.testsuite.test.class=testsuite.simple.StringUtilsTest test

    You can also run individual tests in a test case by specifying the names of the corresponding methods in the com.mysql.cj.testsuite.test.methods variable, separating multiple methods by commas; for example:

    shell > ant -Dcom.mysql.cj.testsuite.test.class=testsuite.simple.StringUtilsTest \
    -Dcom.mysql.cj.testsuite.test.methods=testIndexOfIgnoreCase,testGetBytes test

While the test results are partially reported by the console, complete reports in HTML and XML formats are provided. View the HTML report by opening buildtest/junit/report/index.html. XML version of the reports are located in the folder buildtest/junit.


How do I find MySQL Connector version?

Check MySQL Version with V Command. The easiest way to find the MySQL version is with the command: mysql -V. ... .
How to Find Version Number with mysql Command. The MySQL command-line client is a simple SQL shell with input editing capabilities. ... .
SHOW VARIABLES LIKE Statement. ... .
SELECT VERSION Statement. ... .
STATUS Command..

Where can I find connector J?

The source code for Connector/J is also available on GitHub at https://github.com/mysql/mysql-connector-j. Connector/J is also available as a Maven artifact in the Central Repository.

What is MySQL Connector version?

MySQL Connector/J is the official JDBC driver for MySQL. MySQL Connector/J 8.0 is compatible with all MySQL versions starting with MySQL 5.6. Additionally, MySQL Connector/J 8.0 supports the new X DevAPI for development with MySQL Server 8.0.

Where is MySQL Connector J installed?

jar file at C:\Program Files\MySQL\MySQL Connector J\mysql-connector-java-5.1. 32-bin.