conditional materialized view refresh and create-replace for the view #87
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.
for issue: #88
hi I've started testing
quary
in the production and hitting dependencies errors: If I follow the logic ofDROP/CREATE
view I can't do it withoutCASCADE
deleting all dependencies. The same withmaterialized views
.I suggest that for the view and materialized view there would be no
DROP
command and then changed creation commands:view
:CREATE OR REPLACE VIEW ...
materialized view
: checking if the view exists first and based on that eitherREFRESH MATERIALIZED VIEW ..
orCREATE MATERIALIZED VIEW ..
. In case ofREFRESH
there is no issue with dependent views.thank you