TableCore
Sign in

Changelog

What changed, version by version.

Written by hand as work lands, for the person deciding whether to take an update. Every published version is here; installers and checksums are in the release archive.

Download TableCoreRelease archive

TableCore 2026.1.0

Unreleased

The first public release. Windows x64 only; macOS and Linux builds are planned.

Added

  • SQL against MongoDB. Write SELECT, JOIN, GROUP BY and the rest in a SQL editor with completion and inline diagnostics, and see the MongoDB operation that will actually run before it runs. Shapes MongoDB cannot answer faithfully are refused with a reason rather than approximated. What TableCore accepts is an explicit list, published in full at SQL support: a keyword, function, operator or literal that is not on it is turned away naming itself, rather than quietly ignored and the query run without it.
  • The raw MongoDB query editor, for the times SQL is the wrong way to say it. Both editors feed the same result grid.
  • A result says when it is not quite SQL's result. Where the engine knowingly decided something SQL decides differently, a note above the rows says what was decided and which part of the generated command decided it, and the footer counts the notes beside the row count. Three things earn one today: a grouped query answering with a value from an arbitrarily chosen row, a division (which is always real here), and a query that compares, sorts or groups a column whose documents disagree about its type. A query with nothing to report shows nothing.
  • A result grid built for results that do not fit in memory. Rows arrive one batch at a time as you scroll, the cursor stays open for the tab that owns it, and a released result is handed back to the operating system rather than held.
  • Document editing with a BSON-aware editor: types are preserved, edits are reviewed before they are written, and _id is never guessed.
  • Explain plans, read back in the terms you asked in — which stage the server chose, what it examined, and what it returned.
  • The server monitor: live operations, the ability to kill one, current metrics, the profiler's collection, replica-set and sharded-cluster status.
  • Collection tools — indexes, validation rules, statistics, and reshaping a collection's documents into a new shape with a preview of what would change.
  • Backups, restore, export, import and migration between connections (Pro), in the layout mongodump produces, so nothing here traps your data in a format only TableCore reads.
  • Connection profiles with SSH tunnels. The connection string and any SSH credentials live in the operating system credential store; settings.json keeps only non-secret metadata.
  • English and Polish throughout, including the engine's diagnostics.
  • Three themes — dark, deep dark and light — and a chromeless window that matches them.
  • In-app updates on Windows, with the download reported rather than silent and the restart always the user's decision.
  • A passwordless account — Google, GitHub, Microsoft or a one-time e-mail link, authorized in the browser. TableCore never sees a password, and it works on the Free plan without signing in at all.
  • When Pro goes away, TableCore says why. A paid entitlement is honoured offline for a bounded window; if that window runs out, or the stored document cannot be used for any other reason, the account icon in the title bar says so and opening it gives the actual reason and the actual fix — reconnect once, correct the computer's clock, sign in again, or update. Nothing is lost when this happens: connections, workspace, tabs and saved queries all stay, and the Pro operations resume as soon as the entitlement is confirmed. An installation that has never had an entitlement, including every Free one, says nothing at all.

Known limitations

  • Windows installers are not code-signed yet, so SmartScreen shows an unverified-publisher warning on first run.
  • macOS and Linux builds are not published.