fix: raise error when table declaration fails due to permissions #1322
+19
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix silent failure when table declaration fails due to insufficient permissions.
Problem
When creating a table with cross-schema foreign keys, if the user lacks
REFERENCESprivilege on the parent schema, the table creation would fail silently:Users only discovered the problem when trying to query the non-existent table later.
Solution
Only suppress
AccessErrorif the table already exists (idempotent declaration). Otherwise, raise with a helpful message:Behavior
Closes #1161
🤖 Generated with Claude Code