Best SQL Editor for Mac, Linux and Windows (2026): 6 Editors for MySQL and PostgreSQL
For developers who query MySQL or PostgreSQL from a Mac, a Linux machine or a Windows PC and want one SQL editor on all three; it compares six editors, and what each does with an UPDATE before you commit.
On this page
You write SQL on a MacBook, the build server runs Linux, and the colleague who reviews your queries is on Windows. For that work, use DbSchema: it installs on all three systems, its SQL Editor is free in the Community Edition, and the editor opens under a diagram of the connected schema, so the foreign keys you join on stay in view. An UPDATE you run in it waits in an open transaction until you press Commit. DBeaver, DataGrip, TablePlus, Beekeeper Studio and DbVisualizer also run on Windows, macOS and Linux, and the tables below show where they differ.
Free Community Edition plus a 15-day Architect trial. No signup. Windows, macOS and Linux.
Three kinds of tool turn up in lists of SQL editors
Lists of the best SQL editors put three kinds of tool side by side. A multi-engine desktop client connects to MySQL, PostgreSQL and other engines from one installation. An engine's own tool covers that engine: pgAdmin 4 is built for PostgreSQL, MySQL Workbench for MySQL, and SQL Server Management Studio runs only on Windows. A code editor with an extension adds a query window to an editor you already use, such as Visual Studio Code with Microsoft's MSSQL extension for SQL Server and Azure SQL.
Some lists still recommend Azure Data Studio. Microsoft retired it on 28 February 2026, and it no longer receives updates or security fixes.
If you query both MySQL and PostgreSQL, from more than one operating system, you need the first kind, and that is the kind this article compares.
Six editors compared on engines, free edition and licence
All six run on Windows, macOS and Linux. They differ in the engines they reach, in what the free edition holds and in how the paid licence is sold. The values come from each vendor's own pricing, download and documentation pages, read on 6 November 2026. Prices are per user and exclude tax.
| Editor | Engines | Free edition | Paid licence |
|---|---|---|---|
| DbSchema | Relational and NoSQL, 100+ on its supported databases page | Community Edition, SQL Editor included | Pro, one-time or monthly (purchase page) |
| DBeaver | Relational in Community; MongoDB, Cassandra and Redis in the PRO editions | Community, open source | Lite 113 USD a year, Enterprise 255 USD a year |
| DataGrip | Relational and NoSQL, over 50 | Free for non-commercial use | Monthly or yearly subscription for commercial use |
| TablePlus | Relational, plus Redis, MongoDB, Cassandra and Elasticsearch | Trial limited to 2 tabs, 2 windows and 2 advanced filters | Basic 99 USD one-time for one device |
| Beekeeper Studio | 26+, MongoDB from the Professional plan | Community Edition, open source | Indie 9 USD a month, Professional 14 USD a month, billed yearly |
| DbVisualizer | Relational, plus MongoDB and Cassandra | DbVisualizer Free | Pro 199 USD the first year, 89 USD a year after |
The licence decides what you keep if you stop paying. DbSchema Pro is sold as a perpetual licence or by the month. A TablePlus licence includes one year of updates and keeps working after that year. The yearly subscriptions of DataGrip and DbVisualizer include a perpetual licence for the version you had, and Beekeeper Studio gives a lifetime licence for the versions released while you paid. Each DBeaver PRO licence covers use, updates and support for one year.
Two free editions carry conditions. DataGrip's free licence is for non-commercial development only, and Beekeeper Studio's Community Edition is meant for individuals, non-profits and businesses with fewer than 10 employees or less than 1 million USD in yearly revenue. DbSchema's Community Edition is free and includes the SQL Editor.
An UPDATE in an open transaction stays private until COMMIT
The difference that matters most on a shared database is one that no feature list shows: whether the UPDATE you just ran is already committed. Both engines commit each statement on its own unless you open a transaction. PostgreSQL 17 wraps a statement outside BEGIN in an implicit BEGIN and COMMIT, and MySQL starts every connection with autocommit enabled. This table holds one account:
CREATE TABLE accounts (id integer PRIMARY KEY, balance numeric(10,2));
INSERT INTO accounts VALUES (1, 100.00);
SELECT @@autocommit, @@transaction_isolation;
The last line is for MySQL, which reports its defaults:
Result · MySQL 9.1.0
| @@autocommit | @@transaction_isolation |
|---|---|
| 1 | REPEATABLE-READ |
An editor in auto-commit mode sends the UPDATE as it is, and it is committed as soon as it runs. An editor in manual-commit mode keeps it inside a transaction. Session A does that by hand here (on MySQL, START TRANSACTION takes the place of BEGIN):
BEGIN;
UPDATE accounts SET balance = 0 WHERE id = 1;
Session B, a colleague or a report connected to the same database, reads the row before and after session A commits:
SELECT balance FROM accounts WHERE id = 1;
Under the default isolation level of each engine, READ COMMITTED on PostgreSQL 17 and REPEATABLE READ on MySQL, a reader never sees a change that is not committed:
Result · PostgreSQL 17.9 and MySQL 9.1.0
| moment | session A sees | session B sees |
|---|---|---|
| after the UPDATE, before COMMIT | 0.00 | 100.00 |
| after COMMIT | 0.00 | 0.00 |
Had session A run ROLLBACK instead of COMMIT, both sessions would read 100.00 again. Without the BEGIN, session B reads 0.00 straight after the UPDATE.
What each editor does with that UPDATE by default
Each editor decides for you whether the BEGIN is there. The vendors document it as follows, read on 6 November 2026:
| Editor | An UPDATE you run in the editor | How the open transaction shows |
|---|---|---|
| DbSchema | Stays in an open transaction | The Commit button blinks |
| DBeaver | Auto-commit on Development and Test connections, manual on Production | Commit and Rollback buttons, a Pending transactions window |
| DataGrip | Tx:Auto or Tx:Manual, chosen for each data source | Commit and Roll Back buttons, shown in Tx:Manual only |
| Beekeeper Studio | Auto or manual commit, switched in the bottom left of the editor | Commit and Rollback buttons, a warning after 9 minutes |
| DbVisualizer | Auto Commit, enabled by default | A status bar count of rows updated since the last commit |
DBeaver ties the mode to the connection type, so a connection marked Production starts in manual commit. In DataGrip, you choose the default mode in each data source's Transaction control setting. Beekeeper Studio offers manual mode on PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, Firebird, CockroachDB and Redshift, and rolls an idle transaction back after 10 minutes unless you keep it alive. DbVisualizer commits each statement unless you turn Auto Commit off for the connection or the editor tab. TablePlus keeps edits made in its data grid pending until you commit them, and its documentation names no commit mode for statements typed in the editor.
DbSchema keeps the transaction open until you commit or roll back
The DbSchema SQL Editor opens under the diagram, so the tables you are joining stay in view while you type the join. Auto-complete suggests table and column names from the connected schema as you type, and Ctrl+Space opens the list when it does not appear on its own.
-
Open the editor Community
Press Editor in the toolbar and choose SQL Editor, or use Query → SQL Editor (Ctrl+E). To start from one table, right-click it on the diagram and choose SQL Editor: the editor opens with a
SELECTof its columns. -
Run one statement or a script Community
Run (Ctrl+Enter) runs the selected text, or the statement at the cursor. Run Script (Ctrl+Shift+Enter) runs every statement in turn and prints one text block per statement. The arrow next to Run Script carries Ignore Errors, and Auto Commit, which commits each statement that succeeds.
-
Commit or roll back Community
An INSERT, UPDATE or DELETE run with Run stays in an open transaction, and the Commit button blinks until you decide. Commit (Ctrl+Shift+C) keeps the change; Rollback (Ctrl+Shift+R) undoes it.
- 1Run executes the statement at the cursor
- 2Modified 1 rows, not yet visible to others
- 3Commit lit until you decide
The SQL button in the editor's toolbar switches the language to Java Groovy or JavaScript, for a script that reads the database and the DbSchema model through the Automation API. The SQL Editor works in every edition, Community included.
DbSchema saves every row of a result, not only the visible ones
The save button in the toolbar of the result grid writes the rows to a file: comma, tab or pipe separated text, XML, Markdown, JSON, or an Excel 2003 or 2007 file. DbSchema runs the query again to write every row, not only the rows that the grid shows. Copy As in the same menu puts the rows on the clipboard as CSV, JSON, XML or Markdown.
When the question needs rows from several related tables rather than one query, the Data Explorer shows the rows of a table and, next to them, the rows linked to the one you click; following foreign keys there needs DbSchema Pro. The Query Builder, which the menus call the Query Editor, writes the join from the foreign keys as you click the tables, and also needs Pro.
DbSchema installs on macOS, Linux and Windows
DbSchema has an installer for each system, plus other packages, as its installation page lists them:
| System | Installer | Other packages |
|---|---|---|
| Windows | .exe | .zip, .msi, and an .exe for ARM-64 |
| macOS | .dmg | .tgz |
| Linux | .sh | .deb, .rpm, .tar.gz, and a .tar.gz for ARM-64 |
The .deb package suits Debian and Ubuntu, and the .rpm package suits Fedora and Red Hat. The Windows installer also runs unattended, for a team that installs DbSchema on many machines.
The other editors package differently. DBeaver Community ships DEB, RPM, TAR.GZ, Snap and Flatpak packages for x86 and ARM, and Beekeeper Studio ships AppImage, DEB and RPM. TablePlus needs macOS 12 or later, and on Windows the .NET Framework 4.8; its documentation adds that some of its databases may not be available yet on Windows or Linux. DbVisualizer offers installers for Windows on x64 and Arm64, and for macOS on Apple silicon and Intel.
The SQL Editor is free in DbSchema Community Edition
Download DbSchema, connect it to your MySQL or PostgreSQL database and run your first query under the diagram. The SQL Editor, the diagrams and reverse-engineering are in the free Community Edition. The Query Builder, following foreign keys in the Data Explorer and saving the model to a file are in DbSchema Pro. A new installation starts with a 15-day trial of DbSchema Architect, which has every feature, and continues as Community Edition afterwards.
Sources
Write SQL next to your schema
DbSchema pairs the SQL editor with a live diagram of the database, so foreign keys are visible while you query. The editor, the diagrams and reverse-engineering are in the free Community edition.