examples · mysql

MySQL wire protocol examples

Four recipes for a client speaking the MySQL wire protocol to an OriginChainDB instance. They were written from a real client driven against the shipping engine - Sequelize 6.37 over mysql2 3.24 - so each one either worked or is marked as refused.

The listener is off by default and is enabled per instance. Read the compatibility reference first - it covers TLS, the two credential models, and the limits these recipes stay inside.

1 / 4

Connect and run CRUD

Open a TLS session, declare a table in code, then insert, select with a filter and an ordering, update, and delete.

2 / 4

Transactions that commit and roll back

Both outcomes, exercised against the engine - including the check that proves a rolled-back block really left nothing behind.

3 / 4

Upsert with ON DUPLICATE KEY UPDATE

The MySQL spelling is translated to the engine's upsert. Why REPLACE INTO is refused instead of mapped to it.

4 / 4

Reflection: what the catalog will answer

The information_schema views that work, the SHOW forms that are refused, and how to keep an ORM off the refused half.

MySQL is a registered trademark of Oracle Corporation and/or its affiliates. OriginChainDB is not affiliated with, endorsed by, or sponsored by Oracle Corporation. OriginChainDB implements a compatible wire protocol so that existing MySQL clients can connect to it; it does not distribute MySQL software.