This repository was archived by the owner on Jul 15, 2025. It is now read-only.
FIX: Scope materialized view existence check to current schema#203
Merged
Conversation
Currently, `mview_exists?` returns true if the materialized view existed anywhere in the database, regardless of the schema. This caused issues after backup restores, where the views may exist in the `backup` schema created during the restore but not in the current public schema. This change ensures the check is scoped to the current schema.
cvx
approved these changes
May 19, 2025
Contributor
Author
|
Thanks @cvx |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Currently,
mview_exists?returns true if the materialized view existed anywhere in the database, regardless of the schema. This caused issues after backup restores, where the views may exist in thebackupschema created during the restore but not in the current public schema.This change ensures the check is scoped to the current schema.