Skip to content

Release 1.0.1 - #42

Merged
ZhuchkaTriplesix merged 2 commits into
mainfrom
release/1.0.1
Jul 11, 2026
Merged

Release 1.0.1#42
ZhuchkaTriplesix merged 2 commits into
mainfrom
release/1.0.1

Conversation

@ZhuchkaTriplesix

Copy link
Copy Markdown
Member

Summary

  • Fix Safe Mode on ClickHouse servers that are already read-only: detect HTTP Code: 164 and retry requests without readonly=1 while keeping client-side AST protection and session limits.
  • Centralize HTTP execution in ClickHouseClient (get_with_query, post_sql, execute_with_readonly_retry) so connect, schema introspection, and queries share the same retry logic.
  • Add database field to assets/connection_form.json for default database selection in Querya Desktop.
  • Ensure packaged .qext binaries are executable (chmod +x in package_qext.sh).
  • Bump extension version to 1.0.1 (Cargo.toml, manifest.json).

Test plan

  • cargo test — 64 tests passed locally
  • Install dist/clickhouse-query-ext-1.0.1.qext in Querya Desktop
  • Test Connection with Safe Mode enabled against a read-only ClickHouse user
  • Expand schema tree and open a table in the workspace
  • Run a SELECT via SQL workspace (F5)

Release

After merge, publish with:

git checkout main && git pull
git tag v1.0.1
git push origin v1.0.1

GitHub Actions (release.yml) will build Linux/macOS/Windows .qext artifacts and attach them to the GitHub Release.

Retry HTTP requests without readonly=1 when ClickHouse already enforces
read-only mode (Code 164). Add database field to the connection form and
ensure packaged binaries are executable.
Apply cargo fmt fixes for CI and replace the verbose architecture
overview with a concise product-focused README.
@ZhuchkaTriplesix
ZhuchkaTriplesix merged commit 0411a46 into main Jul 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant