Skip to content

spec 022: duckdb-acl after spec 150 stage 4a - #22

Merged
VGSML merged 1 commit into
mainfrom
022-pin-duckdb-acl-4a
Nov 6, 2026
Merged

VGSML merged 1 commit into
mainfrom
022-pin-duckdb-acl-4a

Conversation

@VGSML

@VGSML VGSML commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Spec: specs/022-pin-duckdb-acl-4a/spec.md.

Moves duckdb-acl from f2f520f (the end of its spec 150 stage 3, which spec 020 followed) to 4acccd7.

duckdb-acl what reaches hugr_node
151 (#279, #280) A principal's DDL record is its own PRAGMA and answers no row. The embedded quack collector skips it.
153 (#281) A client's DDL over Flight runs as text.
154 (#282) A principal's catalog record follows the client's ROLLBACK.
155 (#283) A principal's error names nothing it was not shown.
150 4a (#284) A name in a management statement is read exactly as duckdb reads an identifier, and every revoke of nothing is refused.

For the CLUSTER rules (spec 020), names follow duckdb's identifier rule:

  • AS <alias>, IN GROUP, SECRET, FROM <repo>, an extension and DEPENDS ON are names. A keyword duckdb does not take as a name (a reserved word, full, left) or a leading digit now needs quotes, and the refusal says so.
  • A setting's name and every value stay words.

Nothing stored changes. The source list, ext-common and quack do not move, and acl-otel stays on its pin.

Tests

Locally with HUGR_NODE_E2E=1 GEN=ninja make:

  • test/sql/*: 14 files, 1043 assertions, green.
  • make test-cpp: 4/4 green.

I did not run the e2e (Keycloak, tresor-server, kista). duckdb-acl 4a's compatibility review checked the names this repository's tests and docs write: all of them still read.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LdLs2iBQygBKtsApdH9Sxi

duckdb-acl f2f520f -> 4acccd7: specs 151 (a DDL's record is a PRAGMA that answers
no row; the embedded quack collector skips it), 153 (a client's DDL over Flight
runs as text), 154 (a record follows the client's ROLLBACK), 155 (a principal's
error names nothing it was not shown) and 150 4a (a name in a management
statement is read exactly as duckdb reads an identifier; every revoke of nothing
is refused). The CLUSTER rules' names follow the identifier rule, a setting's name
and the values stay words. No source list, ext-common or quack move.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LdLs2iBQygBKtsApdH9Sxi
@VGSML
VGSML merged commit 49b94cc into main Nov 6, 2026
2 checks passed
@VGSML
VGSML deleted the 022-pin-duckdb-acl-4a branch November 6, 2026 10:10
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