We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
When running DROP VIEW EXISTS on a name that does not exists, a comment about skipping it is output, and the result is DROP_MATERIALIZED_VIEW.
DROP_MATERIALIZED_VIEW
No response
DROP VIEW IF EXISTS test; (with test not existing)
DROP VIEW IF EXISTS test;
The normal DROP_VIEW
Via docker compose
PostgreSQL 9.5-RisingWave-1.5.4 (49a6b42)
It's a very minor bug but I was triple checking the naming / the commands used, so just a bit confusing.
The text was updated successfully, but these errors were encountered:
DROP VIEW IF EXISTS
TennyZhuang
Successfully merging a pull request may close this issue.
Describe the bug
When running DROP VIEW EXISTS on a name that does not exists, a comment about skipping it is output, and the result is
DROP_MATERIALIZED_VIEW
.Error message/log
No response
To Reproduce
DROP VIEW IF EXISTS test;
(with test not existing)Expected behavior
The normal DROP_VIEW
How did you deploy RisingWave?
Via docker compose
The version of RisingWave
PostgreSQL 9.5-RisingWave-1.5.4 (49a6b42)
Additional context
It's a very minor bug but I was triple checking the naming / the commands used, so just a bit confusing.
The text was updated successfully, but these errors were encountered: