Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.3.0 was released on 2024-10-24. This release is of GA (generally available) maturity. It is compatible with MariaDB Connector/R2DBC 1.2 and is the maintenance path for version 1.2. This release is compatible with R2DBC 1.0.0 specification.

Notable Changes

• Support of the PARSEC Authentication Plugin which is provided starting with MariaDB Server 11.6. See the for more details ()

  • This requires Java 15+ (to use Java native ed25519 Algorithm implementation). For previous versions of Java, this will require adding BouncyCastle as a dependency.

Resources

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.2.2 was released on 2024-09-13. This release is of GA (generally available) maturity. It is compatible with MariaDB Connector/R2DBC 1.1 and is the maintenance path for version 1.1. This release is compatible with R2DBC 1.0.0 specification.

Notable Changes

• To support the R2DBC 0.9.1 specification (used by Spring Boot 2.7) the maven artifact org.mariadb:r2dbc-mariadb-SPEC-0.9.1 has been added ()

  • The artifact will be maintained until enterprise support ends for Spring boot 2.7

• A new option, skipPostCommands, permits disabling initial connection settings, and indicating that commands after connections must be skipped. This allows avoiding unnecessary commands on connection creation and, when using RDS proxy to not have session pinning. ()

Issues Fixed

When using connection redirection, error "Connection is closed. Cannot send anything" might be returned. ()

Resources

1.3

1.2

1.1

1.0

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.0.3 was released on 2021-09-27. This release is of General Availability (GA) maturity. This release implements the R2DBC 0.8.5. specifications.

Issues Fixed

• MariadbResult.getRowsUpdated() method fails with ClassCastException for commands with result-set. ()

• Netty buffer leaks when not consuming results. ()

Resources

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.0.0 was released on 2020-12-11. It is the first generally available (GA) release of MariaDB Connector/R2DBC. This release is compatible with R2DBC 0.8.3 specification.

Notable Changes

• MariaDB Connector/R2DBC now supports R2DBC specification version 0.8.3.

Issues Fixed

• Connector releases row before client use. ()

• Row buffer reading position is sometimes incorrect.

• Retained buffer is not released. ()

• Batching on statement use parameters is not added. ()

Resources

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.0.3 was released on 2021-09-27. This release is of General Availability (GA) maturity. This release implements the specifications.

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.1.3 was released on 2022-12-23. This release is of GA (generally available) maturity. This release is compatible with R2DBC 1.0.0 specification.

Notable Changes

• To support the R2DBC 1.0.0 specification, the following implementation has been added or changed:

  • Result.getRowsUpdated() now returns Mono. Prior to this release, Result.getRowsUpdated() returned Mono.

• The default Netty hostname verifier is now used. Prior to this release, a custom hostname verifier was used. ()

• Add SSL Tunnel mode:

Issues Fixed

• When subscriber cancellation occurs before the response ends, the connection might stall. ()

• When a query returns a multi-row resultset, an IllegalReferenceCountException exception occurs in the TextRowDecoder.setPosition() call. ()

• SSL host name verification does not properly close the socket when verification fails. An error is returned for SSL host name, and the connector fails with a socket close error. ()

• When a connection error occurs, the connection is not always properly closed. (

• During failover, the redo buffer is not released before it is garbage collected. ()

Resources

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.0.1 was released on 2021-03-11. This release is compatible with R2DBC 0.8.4 specification.

Notable Changes

• MariaDB Connector/R2DBC now supports R2DBC specification version 0.8.4.

Issues Fixed

• Ensure autocommit initial state. ()

• New option autocommit that defaults to true

• Transaction in query flux might not be persisted. ()

• Data with size bigger than 16Mb correction. ()

Resources

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.0.2 was released on 2021-07-19. This release is compatible with R2DBC 0.8.5 specification.

Notable Changes

• Columns of type Bit(1) and TINYINT(1) are by default converted to Boolean when getting value without type (new option tinyInt1isBit reverts this behavior). ()

Issues Fixed

• Statement :: add not needed after the last binding, as stated in the specification ()

• Errors like too many connections are not handled correctly on socket creation ()

• Some options are not parsed when using a connection string. ()

• Mutual authentication not done when using <<code>>sslMode=TRUST<. (

Resources

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.2.1 was released on 2024-06-24. This release is of GA (generally available) maturity. It is compatible with MariaDB Connector/R2DBC 1.1 and is the maintenance path for version 1.1. This release is compatible with R2DBC 1.0.0 specification.

Notable Changes

• Adding missing UUID Object support ()

Issues Fixed

• NPE if No HaMode provided ()

• Correcting possible bug connecting if project contain a project.properties file ()

• No encoding set for ByteBuffer parameter ()

• Wrong default return type for MySQL JSON fields ()

Resources

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.2.0 was released on 2024-02-23. This release is of GA (generally available) maturity. It is compatible with MariaDB Connector/R2DBC 1.1 and will therefore also be the maintenance path for version 1.1. This release is compatible with R2DBC 1.0.0 specification.

Notable Changes

• New timezone option ()

  • The new timezone option can have 3 types of values:

    • disabled (default) : connector doesn't change timezone

    • auto : connector will set timezone connection variable to java default timezone

r2dbc:mariadb://user:pwd@localhost:3306/db?timezone=+5:00r2dbc:mariadb://user:pwd@localhost:3306/db?timezone=autor2dbc:mariadb://user:pwd@localhost:3306/db?timezone=America/New_York

• The recommended setting for timezone is auto.

• Add support for connection redirection ()

  • With MariaDB Community Server 11.3.1 a new global variable redirect_url value has been added, supported format:

• When set, all existing connections will be redirected to the designated URL values when appropriate. A connection will only be redirected when no transaction is active.

• Example for enabling the redirection:

• The redirection feature is enabled by default. It can be disabled by setting the new option permitRedirect to FALSE, which will result in ignoring the redirection URL.

Issues Fixed

• Properly end connection (in place of RST TCP packet) ()

• Failover High availability mode r2dbc:mariadb:[sequential|loadbalancing]:... wrongly parsed ()

• Compatibility with ()

• Java 8 compatibility regression ()

Resources

Overview

MariaDB Connector/R2DBC is a non-blocking interface between Java applications and MariaDB Server. MariaDB Connector/R2DBC enables the development of Java 8+ applications for MariaDB database products.

MariaDB Connector/R2DBC 1.1.4 was released on 2023-03-27. This release is of GA (generally available) maturity. This release is compatible with R2DBC 1.0.0 specification.

Notable Changes

• When MariaDB Connector/R2DBC 1.1.4 connects to a pre-existing TLS tunnel, host verification can be disabled. ()

  • The behavior can be configured using the , which defaults to false.

  • When the sslMode connection parameter is set to , host verification can be disabled by setting sslTunnelDisableHostVerification to true.

  • For example:

• When the is enabled, prepared statements can use the text protocol. ()

  • To use the text protocol in this scenario, prefix the query string with /text/ when creating the prepared statement.

  • For example, to use the text protocol with the native R2DBC API:

• • Or to use the text protocol with Spring Data:

• MariaDB Connector/R2DBC 1.1.4 adds support for decoding TIMESTAMP and DATE "zero" date values ('0000-00-00') from MariaDB Xpand. ()

  • In previous releases, when the connector received a "zero" date value from Xpand, the value could not be decoded and the following error would be raised:

Issues Fixed

• When the is enabled, MEDIUMINT values are not properly decoded. ()

  • In Connector/R2DBC 1.1.2 and 1.1.3, when the binary protocol is used, the last byte of a MEDIUMINT value is not read from a result-set, so remaining values from the same row are read incorrectly.

• When the Statement.returnGeneratedValues() method is called when connected to a version of MariaDB Server prior to 10.5, an error is raised. ()

• MariaDB Connector/R2DBC's internal statement parser improperly classifies user-defined variables in SELECT statements as named statement parameters. ()

  • In previous releases, the @amount token in the query below would be classified as a named statement parameter, instead of a user-defined variable.

• Since a statement parameter does not exist with that name, the following error would be raised:

• Starting with this release, the internal statement parser can distinguish between user-defined variables and named statement parameters.

• When a ConnectionFactory is used to construct a connection string from a ConnectionFactoryOptions instance, the restrictedAuth, rsaPublicKey, cachingRsaPublicKey, and allowPublicKeyRetrieval connection parameters are not properly parsed. ()

• When a server does not advertise the CLIENT_SESSION_TRACK capability (such as old versions of MariaDB Server, MySQL, and MariaDB Xpand), the MariadbConnection.getTransactionIsolationLevel() and MariadbConnection.setTransactionIsolationLevel(IsolationLevel isolationLevel) methods do not properly get or set the transaction isolation level. ()

Resources