CREATE OR REPLACE...AS no longer works if there are downstream views that reference the target table about duckdb HOT 5 CLOSED

That PR is not relevant here, this one is
#11493

Views create dependencies now

from duckdb.

Doesn't requiring the use of DROP...CASCADE defeat the purpose of CREATE OR REPLACE

I don't agree, I just think what is missing here is the option to provide CASCADE to CREATE OR REPLACE
They control two different intentions

CREATE OR REPLACE indicates your intent to drop the table, it doesn't necessarily indicate your intent to drop the views/indexes/sequences, etc.. that have a dependency on the table

We could argue whether the VIEW should be recreated instead of dropped if CASCADE is provided, but that's a different discussion. I don't think performing a CASCADE implicitly when OR REPLACE is used is the right move

from duckdb.

We could argue whether the VIEW should be recreated instead of dropped if CASCADE is provided, but that's a different discussion. I don't think performing a CASCADE implicitly when OR REPLACE is used is the right move

I do believe that CREATE OR REPLACE should not be destructive towards downstream dependencies. With or without CASCADE.

A typical use case for CREATE OR REPLACE is to atomically refresh the entire table / view without changing the schema and without exposing the clients to partial (empty) data caused by the intermediate table truncation step. Though the argument can be made that this can be achieved by doing these 2 steps as part of a transaction. But this doesn't help with views.

Another use case is to change both data and the schema of the table in a non-descrtuctive way.

The existing behavior renders the latter use cases impossible. Is there a way to disable binding for views and go back to previous behavior?

from duckdb.

This also broke us, for me this is really unexpected. CREATE OR REPLACE should really not be destructive, and it's heavily breaking

from duckdb.

#12209 adds a new setting for view dependencies (enable_view_dependencies) which now defaults to false

from duckdb.