Application developer guide

For developers building applications with v4.2.5, this guide connects first access with production readiness. Source contributors use contribution preparation.

First application path

  1. Record actual version, endpoints and accounts on an isolated instance; do not commit root credentials.

  2. Choose drivers and verify binding, pooling, timezone and Decimal/UInt64/JSON/binary round trips.

  3. Design keys, constraints, types and indexes through schema design, then inspect realistic distributions.

  4. Handle success, statement errors, transaction aborts and unknown commits separately. Design idempotency/timeouts/retry beyond message matching.

  5. Add queries/search/externals with expected results and actual execution paths before scaling.

Tutorials to applications

Stage

Entry point

Acceptance

Connection/CRUD

Language tutorials/drivers

Actual reads/writes, binding, commit/rollback

Transactions

Transactions

Concurrency, error scopes, idempotency/recovery

Analytics

JOIN, EXPLAIN

Correct results, plans and realistic data

AI search/workspaces

RAG, branches

Embedding/model sources, quality, permissions/review

GIS

Types/functions

SRID, units, boundaries and client representation

Ingestion/tools

Ecosystem, CDC

Writes/deletes/schema, checkpoints and destination commits

Production/recovery

Security, backup

Least privilege, TLS, capacity, monitoring and independent restore

Before production

Pin server/driver/connector/Operator versions and flags. Check MySQL compatibility for ORM reflection, DDL, transactions, timezone and return types. Connecting does not certify binlog-source or every ecosystem operation.

Optimize correctness/grain/plans before scans, join distribution, memory/spill and cache/I/O. Report data, hardware, concurrency, duration and failures with performance.

After single-node tutorials validate disconnections, cancellation, restarts and recovery on the target topology. Database rollback does not automatically undo external files, model services or connector effects. Deployment/backup tools have independent versions and require actual restore rehearsal.

Driver charset and returned-value probe

Validate handshake charset separately from result-column metadata. A minimal v4.2.5/mysql2 3.22.6 query on 2026-10-14 returned 空间���� for 空间😀, with column charset 33, while server HEX contained the correct UTF-8 bytes. PyMySQL with utf8mb4 returned the original value. This observation covers that combination only.

SELECT HEX('空间😀') AS utf8_bytes;

Expected: E7A9BAE997B4F09F9880. Also query the original string through the actual driver, compare characters and retain field metadata. A supported handshake collation does not automatically repair result decoding. Applications needing non-BMP characters should mark this combination as requiring a fix/adaptation validation and independently verify conversion paths rather than certifying compatibility from connection success.