Skip to content

Commit d119c0a

Browse files
docs(schema): drop stale fence-attachment guidance
Remove the leftover schema.sql comment for the deleted blanket fence bootstrap, and stop the attach helper's header from telling authors to fence new tables, which contradicts docs/database.md Rule 1. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Signed-off-by: Nikolaj Goodger <[email protected]>
1 parent 7892f0b commit d119c0a

2 files changed

Lines changed: 3 additions & 5 deletions

File tree

‎schema/functions/attach_community_write_fence.sql‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
-- Attach the universal fence to one community-scoped relation. Future
2-
-- migrations must invoke this helper explicitly after CREATE/ALTER introduces
3-
-- community_id; the migration lint enforces that contract.
1+
-- Attach the legacy universal fence to one community-scoped relation. Only
2+
-- tables fenced before fence retirement use it; new tenant tables rely on
3+
-- application admission and must not call it (docs/database.md Rule 1).
44
CREATE FUNCTION attach_community_write_fence(target REGCLASS) RETURNS VOID
55
LANGUAGE plpgsql AS $$
66
DECLARE

‎schema/schema.sql‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -207,5 +207,3 @@ CREATE EXTENSION IF NOT EXISTS pgcrypto;
207207
\i seeds/operator_listener_outbox.sql
208208
\i seeds/relay_operator_audit.sql
209209
\i seeds/storage_accounting_snapshots.sql
210-
211-
-- Fence any community-scoped table that lacks an explicit attach.

0 commit comments

Comments
 (0)