HeidiSQL 12.21 release with index size and column in database tree

ansgar's profile image ansgar posted 2 weeks ago in Anouncements Permalink

Get it from the download page

Notable changes

  • feature: table editor shows size of indexes in separate column

  • feature: show columns as children of tables, in database tree

  • fix: always enable release link label on update check dialog, which points to the general download page

  • fix: CAST(x AS CHAR) not supported by MySQL below v4.0.2

  • fix: refresh session list after import settings file

  • fix: crash during refresh on disconnected session

  • fix: bad width of collation combo box

  • fix: hang when selecting a lot of records and trying to copy/right click

  • fix: on PostgreSQL and SQLite, "Explain current query" does nothing and executes an empty string

  • Linux/macOS: rich text and icons in SQL completion proposal

  • Linux/macOS: refactor parsing the command line

  • Linux/macOS: fix various too narrow number inputs in Preferences

  • Linux/macOS: give the trees and grids more height for the header

  • Linux/macOS: experimental user manager for PostgreSQL

  • Linux: fix column selection context menu with right-click does not work

  • macOS: fix app bundle always reporting version 1.0, affecting Munki, Jamf, Microsoft Intune and others

  • macOS: fix "File > New Window" does nothing

  • macOS: fix: crash when cancelling session manager while a session rename is active

  • Update MariaDB Connector/C to v3.4.9

  • Update libssl and libcrypto to v3.5.7, fixing CVE-2026-31790 and CVE-2025-15467

  • and more: https://github.com/HeidiSQL/HeidiSQL/releases/tag/v12.21

Note: You can already get a preview of v13 for Windows, built on the same codebase as the Linux version. See the download page for a zip package.

index sizes
completion proposal on Linux
table columns in tree
number inputs on Linux

lourdas's profile image lourdas posted 6 days ago Permalink

Excellent work. The new version is much more usable in Linux, because of a few but important (at least for me) details that are now fixed. I've been using the Qt6 build without any issues. Thank you!

Please login to leave a reply, or register at first.