VisuaLeaf v1.0.2686 Release Notes

VisuaLeaf v1.0.2686 Release Notes

Release Date: November 3, 2026

Covers 1.0.2678 – 1.0.2686.

Headline: Safer Batch Operations, Connection Errors That Say What's Wrong, and Smoother Linux Updates

Batch operations now only touch the rows you picked. In MongoDB, choosing "Selected Documents" with
nothing selected could update or delete the whole collection. That can no longer happen. **SQL Batch
Update works for the first time**, on every engine.

Failed connections now tell you why. Instead of "500 Server Error" or a 30-second wait, you get the
server's real reason and a short What to check hint. A MongoDB connection to a server that's down
fails in seconds. When a MySQL or TiDB server requires encryption, VisuaLeaf turns it on and tells you.

Also shipping: insert a MongoDB document from a template built from the collection's validation
rules, validation rules shown on every field, accurate PostgreSQL row counts in Table Stats, and
Linux updates that close and reopen the app for you.

Batch Operations

What stopped happening

• No more whole-collection updates or deletes by accident. In MongoDB's grid and tree views, "Selected

Documents" is greyed out when nothing is selected, and the dialog opens on All documents or
Current search instead. Before, an empty selection meant every document in the collection.

• Selecting a field in the tree view targets only its own document. It used to also hit every other

document with the same value in that field.

• SQL Batch Update works. It used to fail every time. Values with apostrophes, booleans and dates now

save correctly on every engine.

• SQL "All rows" is honest about what it does. With a filter on, it now says it will empty the whole

table instead of showing the filtered row count. The filter preview shows just the condition.

• A filter can never quietly widen to the whole table. Batch update and delete refuse a request that

names no rows, no filter and no "all rows" choice.

• The grid tidies up after a delete. The Batch Delete dialog closes when it succeeds, the deleted rows

are no longer highlighted, and a document whose _id is 0 is no longer skipped.

• CrateDB grids stop showing rows you just deleted.

What you can see

• Redesigned MongoDB Batch Insert, Update and Delete dialogs that match the rest of the app. Their

options stay on one line in narrow windows.

MongoDB Validation Rules

What you can see

• Each field's rules in the Schema Builder. View mode shows rules as small chips (≥ 2000,

len 1–120, items ≥ 1, unique, the pattern, and so on), with a tooltip explaining each one.
(SOZO-1693)

• Rules in the data viewer. Opening a value shows a Rules chip listing that field's rules. Opening a

whole document lists every field that has rules, by name. This only appears for collections with a real
validator, never for a schema guessed from sample documents.

• A heads-up for "constraint" validation. The JSON Schema Builder explains when a collection's rules

can't be changed because of its validation level. (SOZO-1695)

What you can do

• Insert a document from a template. Batch Insert has a new Template option that builds a starting

document that passes the collection's validator: required fields first (also listed above the editor),
allowed values, numbers within range, and strings and arrays long enough. Without a validator, the
template comes from fields found in existing documents. (SOZO-1694)

• Template opens by default on a collection with a validator, since an empty document would almost

always be rejected. You can still switch to Custom JSON.

Connections

What you can see

• The real reason a connection failed, plus a What to check hint, on every MongoDB, SQL and Redis

error. The SQL connection form used to show "500 Server Error" for every failed test.

• Clearer wording for common problems: a wrong SSH key passphrase, a jump host that refused the

connection, a connection timeout, an IPv6-only host, or a wrong replica set name. The connection form
keeps these messages instead of replacing them with a generic one.

• A stopped server is no longer called a TLS problem. When a MongoDB server simply isn't running (a

stopped Docker container, for example), the error says so.

• "Connected with TLS." When a MySQL, MariaDB or TiDB server refuses unencrypted connections, VisuaLeaf

retries with encryption and tells you, in the test result and as a toast when you connect. The form saves that choice
for you, and never overrides a TLS mode you picked yourself.

What you can do

• Find out in seconds that a MongoDB server is down. A connection ends as soon as every server has failed, or a

mongodb+srv address can't be found, instead of waiting 30 seconds.

• Connect to MySQL and TiDB servers that require encryption without changing any settings.
• Use certificate files with PostgreSQL and MySQL in the desktop app. CA and client certificate

settings in Advanced driver properties are accepted when you save, instead of being refused.
PostgreSQL's channel binding setting is accepted too.

• Reach Neon through an SSH tunnel. It used to fail every time. **Full certificate checking also

works through a tunnel now** for PostgreSQL and MySQL; before, it always failed.

Improvements

Table Stats

• PostgreSQL row counts you can trust. A table that had never been analyzed could show 0 rows forever

even when full of data. Those tables are now counted exactly. Very large ones show an estimate as ~N,
with a hint to run ANALYZE for an exact number, in both the Tables Info grid and Table Management's
Storage tab. (SOZO-1690)

Updates and Quitting

• Linux updates close and reopen the app for you. Updating from inside the app on Linux (.deb or .rpm)

now asks first (Install and Reopen / Not Now, plus the usual question about unsaved work), closes
VisuaLeaf while the installer runs, and starts the new version when it's done. Before, the app kept
running while its own files were replaced, which could make it crash, or stop loading data until you restarted it.

• Reopening right after quitting works. Quitting now waits for VisuaLeaf to fully shut down. Before,

reopening within a few seconds could fail to start, or take much longer while it cleaned up.

• Clicking the app while it's closing reopens it once it has finished closing, instead of doing

nothing. This works when you launch it again on Windows and Linux, and from the Dock on macOS.

Notes

• Linux users: the in-app update now closes VisuaLeaf while the installer runs. Save your work when it

asks; the new version opens on its own when the install finishes. If you cancel the installer,
VisuaLeaf won't reopen by itself. Start it yourself. This starts with the update after this one. For
this update, close VisuaLeaf before clicking Install in your system installer.