Altinity / Altinity/altinity-sql-browser
GS: Linked-sheet resource and ClickHouse binding storage
Nobody has claimed this yet.
- 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.mddocs/design/google-sheets/configuration.mddocs/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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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