What is msmp?
An Apache licensed MySQL/MariaDB pure protocol library using scran decoders and narcs encoders. An example client Erlang/OTP 26+ is msc that includes replication using this library.
Protocol Support
The main motivation of this library is to provide good support for binary replication in both MySQL and MariaDB.
Replication Protocol
This section covers the binlog protocol used by MySQL and MariaDB for binary replication.
The following binlog events are supported for binary replication via msmp_binlog_event.
- annotate_rows
- anonymous_gtid_log
- binlog_checkpoint
- delete_rows
- delete_rows_compressed_v1
- delete_rows_v1
- format_description
- gtid
- gtid_list
- heartbeat
- heartbeat_log
- intvar
- previous_gtids_log
- query
- query_compressed
- rotate
- stop
- table_map
- update_rows
- update_rows_compressed_v1
- update_rows_v1
- write_rows
- write_rows_compressed_v1
- write_rows_v1
- xid
The following binlog field types are supported when rows are being updated, written or deleted:
- bit
- blob
- date
- datetime2
- double
- enum
- float
- int24
- JSON (the binary JSON data type)
- long
- longlong
- newdecimal
- string
- time2
- timestamp2
- tiny
- varchar
- year
Binary Protocol
There is also a binary protocol used to prepare, bind and execute statements. Though the field types and encoding used are separate to the ones used by replication.
- msmp_binary
- msmp_binary_resultset_row
- msmp_column_count
- msmp_column_definition
- msmp_com_stmt_close
- msmp_com_stmt_execute
- msmp_com_stmt_prepare
- msmp_com_stmt_prepare_ok
- msmp_com_stmt_reset
- msmp_com_stmt_send_long_data
Text Protocol
The text protocol is used for simple query:
Connection Phase
The following are used in the connection phase of the protocol to negotiate capabilities between the client and server, requesting SSL (TLS), authentication and completing the handshake.