Monghoul

Monghoul 2.0: PostgreSQL, ClickHouse, SQLite and Redis

Monghoul 2.0 opens PostgreSQL, ClickHouse, SQLite and Redis beside MongoDB. What each engine gets, what it does not get, and what stays the same.

· ·checked against Monghoul 2.0.0-rc.1
Five squares of one size in a row. The first is solid black. After a small blue square come four outlined squares, each built another way: one with a small black square inside, one cut into tall strips, one of three nested outlines, one in quarters with one quarter filled.
One square, five ways: MongoDB first, then the four engines 2.0 adds, each in the same window and each drawn its own way.

Monghoul 2.0 opens four more databases: PostgreSQL, ClickHouse, SQLite, and Redis with Valkey. They sit in the same window and the same sidebar as MongoDB. They use the same editor, the same result grid and the same tools, where the engine has the thing a tool reads.

One dialog, five engines

Create Connection has a Database type list, and the form follows the type. PostgreSQL and ClickHouse take a host and a login. SQLite takes a file that you pick in the system’s file dialog, with no server. Redis takes a host and a database number. On each new engine, Test Connection names the version it found.

PostgreSQL

Completion reads your schemas, and after JOIN it offers joins from your foreign keys. Explain shows the plan with real rows and times beside the estimates. You can edit rows in the result grid: Review Changes shows each old value above the new one, and Apply runs every change in one transaction. Manual commit keeps the writes of a tab in one transaction until you click Commit. PostgreSQL in Monghoul.

ClickHouse

Explain plans a SELECT without running it and counts the granules the read selects, so you see whether the sorting key pruned the read. Drafts read {name:Type} parameters. Grid edits work on a MergeTree table by its sorting key. ClickHouse has no transactions, so the review says that each stage commits on its own, and a mutation asks first because ClickHouse cannot undo it. ClickHouse in Monghoul.

SQLite

Monghoul opens a .db, .sqlite, .sqlite3 or .db3 file directly. Values show as SQLite stored them: a 64-bit integer keeps every digit, and a BLOB shows as bytes. Explain shows EXPLAIN QUERY PLAN as a tree, and every change of a grid edit is applied in one transaction. Stop ends a statement at once, because it ends the background process that runs it. SQLite in Monghoul.

Redis and Valkey

The key browser reads keys with SCAN, never KEYS. The editors open a hash, list, set, sorted set, stream or JSON document, and stage your changes until you click Apply. Before it writes, Monghoul checks the values you saw against the key, and writes nothing if another client changed them. In the console, a command that can delete data asks first, with the reasons and the exact command. Redis and Valkey in Monghoul.

What every engine shares, and what it does not

Write protection, operation logs, import, export and AI assistant access work on all five engines. On PostgreSQL, ClickHouse and SQLite, a statement that can drop data or change every row asks first and names the reason, such as “every row (no WHERE)”. A feature that reads something an engine does not have stays off on that engine:

  • Redis has no Explain, no Database Map, no Generate Data and no Schema window.
  • Manual commit is on PostgreSQL only.
  • SQLite has no Cluster Monitor.

The databases page has the full table.

Upgrading from 1.x

On the first launch, 2.0 copies your 1.x data file into a file of its own and never changes the old one, so the 1.x file stays as the backup. While the upgrade runs, the loading screen says “Upgrading your data. This can take a few minutes.” When an upgrade step fails, Monghoul rolls it back, and the message gives numbered steps to restore the backup and go back to the version that wrote it.

Free and Pro

The split is the same on every engine. The free tier has 8 connections and the editors, drafts, results and grid edits. The Cluster Monitor and AI assistant access need Pro on every engine that has them, and so does Export keys on Redis. Pro is one lifetime licence, and it includes every update, 2.0 among them. Pricing.