QueryNot 0.1.15

QueryNot 0.1.15

This release adds estimated query-plan inspection for SQLite, MySQL, MariaDB, and the existing PostgreSQL development preview while preserving QueryNot's local-first and non-executing safety boundaries.

Highlights:

• adds a dedicated Explain action for exactly one selected or caret statement, using the active tab's isolated database session and replacing prior query results;
• requests only EXPLAIN QUERY PLAN on SQLite, EXPLAIN FORMAT=JSON on MySQL and MariaDB, and EXPLAIN (FORMAT JSON) inside the PostgreSQL preview;
• presents native engine facts in bounded Tree and lossless Raw views, with exact raw copy and no index or tuning recommendations;
• normalizes SQLite rows, MySQL and MariaDB JSON variants, and PostgreSQL JSON while retaining Raw-only output when a native shape is unknown or too complex;
• records Explain success, failure, and cancellation in local History without persisting plan payloads or automatically rerunning Explain when SQL is reopened; and
• gives multiple query result sets the same compact underlined view switch as Tree and Raw, including Arrow, Home, and End keyboard navigation.

QueryNot never generates EXPLAIN ANALYZE for this feature. It rejects already-prefixed EXPLAIN or ANALYZE input and multi-statement selections, never asks for destructive approval, fails plans larger than 4 MiB, and limits normalization to 1,000 nodes and 64 levels. Estimated Explain for data-changing statements asks the engine for a plan without executing the source statement.

PostgreSQL remains a development preview. Its dedicated PostgreSQL 18.6 conformance fixture and support evidence are still pending, so this release does not add PostgreSQL to the supported database matrix.

QueryNot remains local-first and sends no telemetry or database information. Connection credentials, direct database access, native session isolation, query-history persistence, TLS verification, destructive-query safeguards, file boundaries, and updater-signing boundaries remain native and fail closed.

Updater signatures authenticate release payloads but are not Windows Authenticode, Apple Developer ID/notarization, or Linux repository signatures. Windows may show an unknown-publisher warning, macOS may require its per-application Open Anyway flow for the unnotarized build, and Linux desktop or package tools may show an untrusted-source warning. Do not disable an operating-system security control globally; verify the downloaded installable package against SHA256SUMS before installation.

The supported platform and database matrix remains unchanged from 0.1.14: Windows 11 x86-64, Linux x86-64 through AppImage/DEB/RPM, macOS 13 or later on Intel and Apple silicon, SQLite format 3, and the published MySQL/MariaDB fixture matrix. Native hardware, Windows Narrator/WebView2 UI Automation, operating-system Contrast Themes, vault, performance, dogfood, and external beta observations remain follow-up evidence rather than release claims.