Bump mariadb-java-client from 2.5.1 to 2.7.3

[dependabot-preview]

Bumps mariadb-java-client from 2.5.1 to 2.7.3.

Release notes

Sourced from mariadb-java-client's releases.

MariaDB java connector 2.7.2

2.7.2 (29 Jan. 2021)

Full Changelog

• CONJ-847 NPE at UpdatableResultSet#close
• CONJ-849 driver now doesn't close connection caused java.io.NotSerializableException as a result of incorrect data bind to a prepared statement parameter
• CONJ-850 MariaDbResultSetMetaData#getPrecision(int) now returns correct length for character data
• CONJ-851 metadata getBestRowIdentifier incompatibility with MySQL 8 correction
• CONJ-853 Support Aurora cluster custom endpoints
• CONJ-852 ON DUPLICATE KEY detection failed when using new line

MariaDB java connector 2.7.1

2.7.1 (23 Nov. 2020)

Full Changelog

• CONJ-834 use of BULK batch is conditioned by capability, not checking server version
• CONJ-835 GSS Imports set in OSGI Bundle
• CONJ-839 Wrong exception message when rewriteBatchedStatements is enabled
• CONJ-841 ResultSetMetaData::getColumnTypeName() returns incorrect type name for LONGTEXT
• CONJ-842 Byte array parameters are now send as long data
• CONJ-837 prepared statement cache leak on ResultSet CONCUR_UPDATABLE concurrency
• CONJ-843 ParameterMetaData::getParameterType for CallableStatement parameter return expected "BINARY" value for BINARY type

minor:

• CONJ-845 test suite now test SkySQL with replication setting
• CONJ-838 have a 'replica' alias for 'slave' connection option

2.7.0

This version is a general availability (GA) release.

Full Changelog

• CONJ-805 - maxFieldSize string truncation occurs on bytes length, not character length
• CONJ-807 - Correcting possible Get Access Denied error if using multiple classloader
• CONJ-810 - normalization of resultset getDate/getTime of timestamp field.
• CONJ-812 - DatabaseMetadata.getBestRowIdentifier and getMaxProcedureNameLength correction
• CONJ-813 - setConfiguration not being called on classes that extend ConfigurableSocketFactory
• CONJ-816 - Table with primary key with DEFAULT function can be inserted for 10.5 servers
• CONJ-817 - Switched position of REMARKS and PROCEDURE_TYPE in the getProcedures result
• CONJ-820 - MySQLPreparedStatement.setObject can now handle java.lang.Character type
• CONJ-828 - new option ensureSocketState to ensure protocol state
• CONJ-829 - Option to cache callablestatement is now disabled by default
• CONJ-830 - connector now throw a better error if SSL is mandatory and server doesn't support SSL
• CONJ-814 - Small possible improvement of getCrossReference, getExportedKeys and getImportedKey
• CONJ-825 - XAResource.isSameRM implementation

MariaDB java connector 2.6.2

This version is a general availability (GA) release.

... (truncated)

Changelog

Sourced from mariadb-java-client's changelog.

Change Log

3.0.0 (3 May 2021)

Full Changelog

This version is a total rewrite of java driver.

• complete rewrite, code clarification, reduced size (15%), more than 90% coverage tested.
• Encoding/decoding implementation are now registred by Codec, permitting codec registry implementation
  • example support of Geometry Object
• Permit authentication plugin restriction by option restrictedAuth
• performance improvement:
  • Prepare and execution are now using pipelining when using option useServerPrepStmts
  • performance enhancement with MariaDB 10.6 server when using option useServerPrepStmts, skipping metadata (see https://jira.mariadb.org/browse/MDEV-19237)

correction:

• CONJ-864 includeThreadDumpInDeadlockExceptions always includes the thread dump, even when it is not a deadlock exception
• CONJ-858 Properties parameter that differ from string not taken in account

Easy logging

If using log4j, just enabled package "org.mariadb.jdbc" log.

level ERROR will log connection error level WARNING will log query errors level DEBUG will log queries level TRACE will log all exchanges with server.

If not using log4j, console will be used. If really wanting to use JDK logger, System property "mariadb.logging.fallback" set to JDK will indicate to use common logging.

Failover

Failover implementation now permit to redo transaction : when creating a transaction, all command will be cached, and can be replay in case of failover.

This functionality can be enabled using option transactionReplay.

This is not enabled by default, because this required that application to avoid using non-idempotent commands.

example:

START TRANSACTION;
select next_val(hibernate_sequence);
INSERT INTO myCar(id, name) VALUE (?, ?) //with parameters: 1, 'car1'
INSERT INTO myCarDetail(id, carId, name) VALUE (?, ?, ?) //with parameters: 2, 1, 'detail1'
INSERT INTO myCarDetail(id, carId, name) VALUE (?, ?, ?) //with parameters: 3, 2, 'detail2'
COMMIT;

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)