Why Tablyne for MySQL
Reviewed MySQL and MariaDB edits, FOR UPDATE checks, SSH tunnels, TLS and safe mode in one desktop client.
The most-voted request connected with this workflow is running queries concurrently - 72 votes when we checked on Nov 12, 2026. Tablyne’s MySQL and MariaDB work is organized around a connection, a data grid and a query console that can stay open together.
Edits that check the row first
A grid edit is staged before it is written. The review SQL contains the changed columns and the identity predicate. When a row version is available, Tablyne starts a transaction, re-reads the row with FOR UPDATE, calculates the current row token and compares it with the token captured by the grid. A changed or missing row rejects the batch before the update or delete is applied.
This matters because a normal repeatable-read snapshot could show an old value. FOR UPDATE makes the re-read see the current row and holds the row lock until the transaction completes. The review text also explains that running the displayed SQL manually does not reproduce the in-memory token comparison.
MySQL and MariaDB details
- SSH tunnels and TLS up to verify CA and server name
- EXPLAIN as text or JSON, not a visual plan
LOAD DATA LOCALis always refused- A grid workflow for staged changes and row inspection
- SQL export with MySQL-specific statement options
Where to go next
- Connect to MySQL or MariaDB with the URL or connection fields.
- Read safe mode and review before editing a production connection.
- Open the MySQL & MariaDB GUI page.
Use Ctrl+S to save pending changes, Ctrl+Z to undo and Ctrl+Y to redo.