Mariadb Connector J Usage

MariaDB Connector/J

Last updated: 2026-08-10

MariaDB Connector/J is the official JDBC driver for MariaDB and MySQL — Maven coordinates org.mariadb.jdbc:mariadb-java-client, LGPL-licensed. This skill covers the connector-specific behavior and the traps that bite generated application code. For adding the driver to a build and configuring the URL, TLS, and pooling, see mariadb-connector-j-install. It is pure Java — it implements the client/server protocol itself and does not depend on MariaDB Connector/C (unlike Connector/Python or Connector/ODBC).

Default context: Assume the 3.5.x line (current release 3.5.10) unless the user states otherwise. Connector versions are independent of the MariaDB server version — a 3.x connector routinely talks to a 10.6/10.11/11.x server.

What LLMs Often Miss

Connection, prepared statements, and a transaction

import java.sql.*;

// JDBC 4 auto-registers the driver — no Class.forName() needed
try (Connection conn = DriverManager.getConnection(
        "jdbc:mariadb://localhost:3306/appdb", "app", "secret")) {

    conn.setAutoCommit(false);   // autocommit defaults to true — turn it off for a transaction

    try (PreparedStatement ps = conn.prepareStatement(
            "INSERT INTO t (name, qty) VALUES (?, ?)")) {
        ps.setString(1, "widget");
        ps.setInt(2, 5);
        ps.executeUpdate();
        conn.commit();
    } catch (SQLException e) {
        conn.rollback();
        throw e;
    }

    try (PreparedStatement ps = conn.prepareStatement(
            "SELECT id, name FROM t WHERE qty > ?")) {
        ps.setInt(1, 0);
        try (ResultSet rs = ps.executeQuery()) {
            while (rs.next()) {
                System.out.println(rs.getInt("id") + " " + rs.getString("name"));
            }
        }
    }
}

Pooling with MariaDbPoolDataSource

import org.mariadb.jdbc.MariaDbPoolDataSource;
import java.sql.*;

try (MariaDbPoolDataSource pool = new MariaDbPoolDataSource(
        "jdbc:mariadb://localhost:3306/appdb?user=app&password=secret&maxPoolSize=10")) {

    try (Connection conn = pool.getConnection();
         Statement stmt = conn.createStatement();
         ResultSet rs = stmt.executeQuery("SELECT 1")) {
        rs.next();
    } // conn.close() (implicit) returns the connection to the pool, it doesn't disconnect
}

Batch insert and generated keys

try (PreparedStatement ps = conn.prepareStatement(
        "INSERT INTO t (name, qty) VALUES (?, ?)", Statement.RETURN_GENERATED_KEYS)) {
    for (Row row : rows) {
        ps.setString(1, row.name());
        ps.setInt(2, row.qty());
        ps.addBatch();
    }
    ps.executeBatch();

    try (ResultSet keys = ps.getGeneratedKeys()) {
        while (keys.next()) {
            System.out.println(keys.getLong(1));   // one id per inserted row
        }
    }
}

RETURN_GENERATED_KEYS has to be requested when the statement is prepared; adding it later has no effect.

See Also

• mariadb-connector-j-install — adding the driver to a Maven or Gradle build, the URL and datasource wiring, and TLS configuration
• mariadb-connector-r2dbc-usage — the reactive, non-blocking sibling driver for Java (also pure Java, no Connector/C dependency)
• mariadb-transactions / mariadb-set-transaction — the server-side semantics behind conn.commit() / conn.rollback() and isolation levels
• mariadb-prepare — server-side prepared statements, what useServerPrepStmts=true uses under the hood
• Canonical reference on mariadb.com/docs, consult for edge cases not covered here: https://mariadb.com/docs/connectors/mariadb-connector-j

This page is: Copyright © 2026 MariaDB. All rights reserved.