omni-sql v0.2.6

0.2.6 (2026-09-10)

Improvements

• indexes: allow primary-key index names and columns to be edited from View Structure, with reviewed drop-and-recreate SQL generated for the change.
• documentation: improve the GitHub project showcase and release presentation.

Bug Fixes

• index editor: keep the index-name and column-search controls focused when clicked inside the Tauri WebView so they accept keyboard input reliably.

Full Changelog: v0.2.5...v0.2.6

omni-sql v0.2.5

0.2.5 (2026-09-09)

Improvements

• results: show compact CSV export notifications with the saved row count and actions to open the file or reveal it in the system file manager.
• formatting: preserve SQL comments and string literals while formatting, and improve configurable formatting behavior in the editor.
• connections: make sidebar drag and drop more reliable and easier to use.

Bug Fixes

• CSV export: open exported files through validated native commands so user-selected paths are accepted without weakening the application permission scope.

Full Changelog: v0.2.4...v0.2.5

omni-sql v0.2.4

0.2.4 (2026-09-08)

Improvements

• MCP: expand the README integration overview with the complete seven-tool surface, local transport flow, approval model, and security boundaries.
• MCP: document a reproducible proposeSqlEdit verification workflow and update the detailed guide for index inspection and query plans.
• dialogs: restore a spacious side-by-side comparison for MCP SQL edit proposals while retaining a stacked layout on narrow screens.

Bug Fixes

• autocomplete: render Monaco completion widgets outside the editor clipping boundary so every suggestion, including All columns, remains visible above the results grid.
• dialogs: apply the standard dialog padding to MCP edit titles, content, and actions.

Full Changelog: v0.2.3...v0.2.4

omni-sql v0.2.3

0.2.3 (2026-09-08)

Features

• table: improve structure editing, column suggestions, scrolling, and reviewable SQL (156b555)
• indexes: add compact cards, ordered columns, search-based selection, and large-table support (e1ecaa6)
• connections: add schema search, selected-first ordering, selection counts, and a clearer all-schemas mode (c8d6c47)
• defaults: suggest default expressions supported by the active database dialect (e1ecaa6)

Bug Fixes

• columns: keep focus and selection in the name field when adding or renaming columns (156b555)
• indexes: preserve combobox input while React applies index-column state updates (9d134cf)
• dialogs: restore balanced sizing, spacing, scrolling, and padded titles and actions (c8d6c47)
• types: preserve sensible defaults after expanding dialect-specific column types (0c46b9d)

Full Changelog: v0.2.2...v0.2.3

omni-sql v0.2.2

omni-sql v0.2.2

omni-sql is an open-source desktop SQL IDE for developers who work across multiple
database engines. It combines schema exploration, a Monaco-powered SQL editor,
contextual autocomplete, query results, guarded row editing, and execution plans in
one local workspace.

v0.2.2 polishes two visible parts of the daily workflow: autocomplete labels now follow
the selected interface language, and table metadata expands reliably from the schema
tree. It also ships with refreshed project visuals and includes all earlier v0.2 desktop
improvements.

New in v0.2.2

• Localized completion labels — the all-columns suggestion now follows the selected
  UI language instead of remaining in Portuguese.
• Reliable schema navigation — expand controls in the metadata tree no longer
  overlap neighboring rows, so the intended table opens consistently.
• Refreshed project presentation — the README and landing page now show the current
  interface, accompanied by a new demo GIF and social preview image.

Highlights across the v0.2 series

• Unified table structure editing — manage columns and supported table structure
  changes through a more consistent editing flow.
• Clearer execution history — query history is easier to scan and use while moving
  between recent statements.
• Improved desktop layout — responsive behavior and visual hierarchy were refined
  across the workspace and dialogs.
• Visible connection context — the active connection, database engine, and database
  are easier to identify while writing and running SQL.
• Better runtime diagnostics — Java validation and release-verification failures
  are surfaced more clearly instead of failing silently.
• Consistent SQL terminology — labels and destructive-statement language are more
  predictable throughout the app.

Supported databases

• PostgreSQL
• MySQL
• MariaDB
• SQL Server
• Oracle
• Generic JDBC (experimental, with limited metadata and execution features)

Downloads

• Windows 10/11 x64: .exe installer
• Debian/Ubuntu amd64: .deb package
• SHA256SUMS: checksums for the published installers

The installers bundle the application runtimes. End users do not need to install
Node.js, Java, Rust, a separate database client, or a vendor client SDK.

Before you start

omni-sql is early-stage software. Try it with a development database before using it
against important environments, and report unexpected behavior through GitHub Issues.

v0.2.2 changelog: v0.2.1...v0.2.2

Complete v0.2 series: v0.1.39...v0.2.2

Documentation: https://github.com/cccadet/omni-sql#readme

omni-sql v0.2.1

Full Changelog: v0.2.0...v0.2.1

omni-sql v0.2.0

Full Changelog: v0.1.39...v0.2.0

omni-sql v0.1.39

Full Changelog: v0.1.38...v0.1.39

omni-sql v0.1.38

Full Changelog: v0.1.37...v0.1.38

omni-sql v0.1.37

Full Changelog: v0.1.36...v0.1.37