mariadb-connector-cpp-usage

Get the driver singleton with sql::mariadb::get_driver_instance(), then call driver->connect(url, props) with a JDBC-style URL like jdbc:mariadb://host:3306/db. The call returns a raw Connection pointer you should wrap immediately in std::unique_ptr.

Call conn->prepareStatement() with positional ? placeholders only, then bind values with setString(1, ...), setInt(2, ...). Parameter indexes are 1-based, and client-side prepared statements are the default unless useServerPrepStmts=true is set.

Both PreparedStatement parameter indexes and ResultSet column indexes are 1-based in Connector/C++. Index 0 or an out-of-range index throws sql::IllegalArgumentException, a subclass of sql::SQLException.

No. Factory methods like connect(), prepareStatement(), and executeQuery() return raw owning pointers with no automatic cleanup. Wrap them in std::unique_ptr or call close() explicitly, destroying children before the parent Connection.

A SQL NULL reads back as the type's zero value, so call ResultSet::wasNull() immediately after getInt() or getString() to distinguish a real 0 from a NULL.

get_driver_instance() returns a process-wide singleton safe for obtaining independent connections from multiple threads, but individual Connection, Statement, and ResultSet objects are not documented as thread-safe. Give each thread its own connection.