Skip to content

Fix recreating indexes for materialized views within custom schemas#364

Open
fatkodima wants to merge 1 commit intoscenic-views:mainfrom
fatkodima:update_materialized_view-and-schemas
Open

Fix recreating indexes for materialized views within custom schemas#364
fatkodima wants to merge 1 commit intoscenic-views:mainfrom
fatkodima:update_materialized_view-and-schemas

Conversation

@fatkodima
Copy link

Fixes #334

When materialized view is created within a custom schema and then we try to update it, the original indexes are not retrieved because of the problem within the used SQL to do that.

@fatkodima fatkodima force-pushed the update_materialized_view-and-schemas branch from 6d1c9ff to 9e47889 Compare July 2, 2022 18:09
@fatkodima fatkodima force-pushed the update_materialized_view-and-schemas branch from 9e47889 to 549e9a3 Compare July 2, 2022 18:11
@fatkodima
Copy link
Author

@derekprior I am sorry for pinging, but can you, please, take a look at this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Indexes are not replaced after upgrading a materialised view

2 participants