Altinity / Altinity/altinity-sql-browser

GS: Linked-sheet resource and ClickHouse binding storage

Open
#400 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cool feature
Dominant language
TypeScript
Stars
8
Forks
2
Avg merge
1h 34m
Merged PRs (30d)
6

Description

Parent: #398
Depends on: #399

Design:

  • docs/design/google-sheets/resource-model.md
  • docs/design/google-sheets/configuration.md
  • docs/design/google-sheets/sharing-security.md

Scope

Add the versioned linked-sheet workspace resource, strict configuration parsing, configured ClickHouse binding and refresh-log services, pinned saved-query snapshots, and binding management UI.

Acceptance criteria

  • Bindings have stable IDs and versioned canonical codecs.
  • One saved query may own multiple bindings.
  • Binding versions are appended through the current authenticated ClickHouse connection.
  • Configured table identifiers are parsed and quoted strictly; no DDL or migration is attempted.
  • Table conformance and privileges produce clear diagnostics.
  • Editing a workspace query does not silently alter a binding.
  • Updating a binding to the current query is explicit and versioned.
  • Workspace export/import preserves non-secret portable metadata and requires revalidation.
  • ClickHouse grants and row policies remain the only binding ACL.

Non-goals

Refresh execution, append cursor logic, application-managed ACLs, or storing credentials.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with parent issue #398 and dependency #399, then read the three design documents: docs/design/google-sheets/resource-model.md, configuration.md, and sharing-security.md. Trace the existing workspace, query, binding, and ClickHouse connection entry points before planning the resource, services, storage, and UI changes. Done means the listed acceptance criteria are met without implementing the stated non-goals.

Written by the indexing model from the issue text.

Assessment

Tech stack
clickhouse, typescript
Domain
backend, databases, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.