feat: reference for the self referencing view error #37560
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
7 Skipped Deployments
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
darora
approved these changes
Jul 31, 2025
| CREATE VIEW v2 AS SELECT * FROM v1; | ||
| ``` | ||
|
|
||
| -- Drop the offending view. |
There was a problem hiding this comment.
stray comment? Can make it a full sentence e.g. Drop the offending view from your database, or delete them from the logical backup to make it restorable.
Co-authored-by: Div Arora <darora@users.noreply.github.com>
valigula
commented
Jul 31, 2025
PLyn
pushed a commit
that referenced
this pull request
Aug 25, 2025
* feat: reference for the self referencing view error * feat: adding format * Update apps/docs/content/guides/platform/backups.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update backups.mdx * Update apps/docs/content/guides/platform/backups.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * feat: linter * Update apps/docs/content/guides/platform/backups.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update apps/docs/content/guides/platform/backups.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update apps/docs/content/guides/platform/backups.mdx Co-authored-by: Div Arora <darora@users.noreply.github.com> * Update apps/docs/content/guides/platform/backups.mdx --------- Co-authored-by: andres.suarez <andres.suarez@supabase.io> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Div Arora <darora@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have read the CONTRIBUTING.md file.
Yes
What kind of change does this PR introduce?
Documentation update
What is the current behavior?
The backups guide mentions invalid-check-constraints errors during logical restores but doesn’t cover other common causes, such as views that reference themselves.
What is the new behavior?
Adds a new subsection under Backups > Invalid Check Constraints explaining how self-referencing views can cause restore failures when using logical backups. Includes examples and a link to the official PostgreSQL documentation.
Additional context
This update helps users troubleshoot and resolve restore issues related to broken view definitions, especially in customer support situations where users encounter errors from invalid or cyclic view references.
https://linear.app/supabase/issue/INDATA-35/add-a-comment-in-the-supabasedoc-or-view-pointing-to-itself