Skip to content

v0.4.1 — Reliability & Engine Fixes

Latest

Choose a tag to compare

@abeni16 abeni16 released this 18 Oct 00:21

What's Fixed in v0.4.1

This patch release closes the three most recent issue reports and hardens several database engines.

🐛 MongoDB & Redis Queries

  • MongoDB queries work again. Every MongoDB query previously failed with "This statement modifies data or schema" because the backend applied the SQL-only read-only guard to non-SQL engines. The guard is now engine-aware, so db.legals.find({}) runs without a false write prompt.
  • Redis commands now execute from the query editor. The generic query path previously returned "Redis uses its own command path"; Redis now supports quoted arguments, logical database selection, password-only auth, rediss:// URLs, and logical DB listing.
  • MongoDB parsing is more robust. Generated previews (db.users.find({}).limit(100)), bare collections, db.getCollection("..."), ObjectId(...), and relaxed JSON filters are supported, with clear errors for unsupported methods.
  • MongoDB connections now add tls=true for non-SRV URIs when SSL mode is require.

🗂️ Create Table / DDL on Empty Databases

  • "Create Table" and "Run DDL script" now work when the database has no tables. Both dialogs were previously unmounted by an empty-state early return, so clicking the buttons did nothing.
  • The migration preview is wired up. Pending CREATE TABLE changes can now be reviewed and applied; previously the dialog was hard-coded to an empty summary.
  • "Download SQL" in the Model workspace now downloads the migration SQL instead of doing nothing.

🔐 SQL Server / Azure SQL Connectivity

  • SSL mode "disable" no longer forces a TLS handshake. EncryptionLevel::Off in tiberius still performs a login TLS handshake; disabled connections now use EncryptionLevel::NotSupported.
  • "Prefer" retries without TLS if the handshake fails, while "Require" and Azure SQL use full TLS with certificate trust.
  • The selected SSL mode is no longer discarded for MSSQL, ClickHouse, and Azure SQL connections.

🗄️ Other Engine Fixes

  • DuckDB numeric, date, and decimal values no longer render as NULL.
  • PostgreSQL multi-statement scripts keep the last result set instead of mixing columns across statements.
  • The write guard now requires confirmation for data-modifying CTEs (WITH ... DELETE) and EXPLAIN ANALYZE <write> statements.

🔧 Under the Hood

  • Added unit tests for the read-only guard, MongoDB parser, Redis argument/reply handling, DuckDB value conversion, MongoDB/Redis connection URLs, and MSSQL encryption mapping.
  • cargo test --lib: 115 passed
  • pnpm test: 93 passed
  • pnpm exec tsc -b and cargo check --all-targets: clean

Upgrading from v0.4.0: drop-in upgrade; existing connections, saved queries, and layouts are preserved.

Full Changelog: v0.4.0...v0.4.1

Fixes #62, #61, #55