Database Tools compatibility with MemCP

Database Tools compatibility with MemCP

MemCP speaks the MySQL wire protocol over TCP and a Unix socket. Compatibility depends on both SQL behavior and the metadata queries issued by a particular client version.

Tool	Connection	Current status	Notes
MySQL CLI	MySQL protocol	Supported	Core SQL, prepared statements, SHOW metadata, and process control
PDO MySQL	MySQL protocol	Supported	Use the MySQL PDO driver
DBeaver	MySQL driver	Supported with limitations	Retest schema editing and metadata against the concrete release
PHPMyAdmin	MySQL driver	Compatibility target	Do not claim a version supported without a dated test run
VS Code SQLTools	MySQL/MariaDB driver	Supported with limitations	No dedicated MemCP extension is required

MemCP implements prepared statements, selected INFORMATION_SCHEMA relations, SHOW metadata, processlist, TCP, and a Unix socket. It does not claim byte-for-byte MySQL server behavior. Record the MemCP commit, client version, connection mode, and failed metadata query when reporting incompatibility.

Connecting a tool

Select a MySQL or MariaDB driver, use the configured host and MySQL port (3307 in the documentation examples), and authenticate with a least-privilege MemCP user. Disable driver features that require an unsupported server capability rather than assuming the connection failure is network-related. For the command line:

<syntaxhighlight lang="bash"> mysql --protocol=TCP -h 127.0.0.1 -P 3307 -u app_user -p myapp </syntaxhighlight>

When a GUI opens a connection but fails while browsing schemas, capture its first failing metadata statement and reproduce that SQL through the CLI. Tool compatibility often depends on those discovery queries rather than ordinary SELECT/INSERT behavior.

Matrix reviewed against MemCP commit c42e19eba on 27 August 2026; individual GUI versions still require concrete verification.