Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Drop refresh SPs for old-style manual matviews that have been replaced with native matviews #145

Open
rod-glover opened this issue Feb 8, 2023 · 2 comments
Open

Drop refresh SPs for old-style manual matviews that have been replaced with native matviews #145

rod-glover opened this issue Feb 8, 2023 · 2 comments

Comments

@rod-glover
Copy link
Contributor

rod-glover commented Feb 8, 2023 •
edited
Loading

The title says it all.

Thus far there is one: vars_per_history_mv_refresh. There will be more.
@rod-glover
Copy link
Contributor Author

All old-stryle manual matviews have now been replaced with native matviews: #26

@rod-glover
Copy link
Contributor Author

Question: Is it the business of PyCDS to manage this nominally external content? I suppose it can be seen so: Apart from the fact that we started management (i.e., migrations) with a well-established database, we also manage the views related to these matviews. So why not the SPs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rod-glover