The tool set is small - one statement runner plus shortcuts for creating tables and inserting rows - and it covers writes. That makes it useful for scaffolding a schema while prototyping, and it makes the privileges on the connecting user the thing worth deciding first.
A MySQL server with a small surface: run a SQL statement, create a table, insert rows. Results come back as JSON, and each transaction is logged under its own ID.
- A SQL statement executed against the database - SELECT, UPDATE and DELETE among them
- A table created from a CREATE TABLE statement
- Rows inserted into a table
- Results returned as JSON, with transaction logging on each call
A reachable MySQL server and its connection settings - host, port, user, password and database name - as environment variables. It writes as well as reads, so the grants on the MySQL user are what bound it.
