What is SQL Gnome?

Who It's For

SQL Gnome is designed for people who work with MySQL data directly:

• Developers
• Technical operators
• Support engineers
• Anyone running database-heavy internal workflows

The app is optimized for inspection, query execution, and targeted data edits. It is not intended to behave like a simplified admin panel.

Capabilities

• Direct MySQL connections
• SSH-tunneled MySQL connections
• Database, table, and view browsing
• Row inspection and direct row editing in Content
• Schema and metadata inspection in Structure
• Ad hoc SQL execution in Query
• Saved queries and query history
• SQL import and export workflows
• Local trial and direct license-key activation

Operating Model

SQL Gnome has three distinct surfaces. They are intentionally separate and don't bleed into each other.

Content

For browsing result sets and editing rows when row identity can be established safely. Row editing is only available when SQL Gnome can identify a row — typically via a primary key or usable unique index.

Structure

For columns, indexes, foreign keys, and other schema metadata. Use this when you need to understand how a table is built, not just what's in it.

Query

For manual SQL execution and result inspection. Supports saved queries and query history. Query execution does not mirror the Content browsing model — these are separate mental modes.

Safety & Constraints

SQL Gnome takes a conservative approach to potentially destructive operations:

• Row editing is only enabled when a row can be safely identified — typically through a primary key or usable unique index.
• Metadata loading is lazy where possible, so normal table browsing isn't blocked by database-wide schema inspection.
• Destructive operations are handled conservatively and are not hidden behind aggressive automation.