Skip to content

QueryNot 0.1.14

Choose a tag to compare

@github-actions github-actions released this 31 Aug 14:03

QueryNot 0.1.14

This release adds QueryNot's first compiled PostgreSQL adapter as a development-preview connection path while preserving the existing SQLite, MySQL, and MariaDB workflows and safety boundaries.

Highlights:

  • adds PostgreSQL server profiles with the standard 5432 default, direct fail-closed TLS, system-trust or custom-CA identity verification, optional client certificates, and the existing native credential and session isolation;
  • adds PostgreSQL 18.x identity classification, schema context switching, tables, views, overloaded routines, columns, keys, indexes, and definitions through the common metadata contract;
  • adds PostgreSQL-aware SQL editing and completion, including dollar-quoted bodies, nested comments, UTF-8 dollar tags, explicit escape strings, numbered parameters, and common PostgreSQL functions;
  • carries bounded acknowledged result streaming, cancellation through pg_cancel_backend, transactions, typed scalar/JSON/UUID/array values, deterministic browsing, and guarded atomic mutations through the native adapter; and
  • keeps saved file/server and server-engine profile kinds immutable at the native boundary.

PostgreSQL 18.6 is the exact planned disposable conformance baseline, but that dedicated password/client-certificate, TLS, metadata, value, cancellation, transaction, and table-mutation fixture is not yet retained. PostgreSQL therefore remains a development preview and is not added to QueryNot's supported database matrix by this release. Other PostgreSQL major versions connect in query-only mode, and the existing release harness refuses to misrepresent its MySQL/MariaDB evidence as PostgreSQL certification.

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.13: 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.