I would like to be able to pre-populate a local duck.db database with VIEWs that can be accessed by other backends that also use duckdb, without resorting to raw SQL code.
Describe the solution you'd like
Most of the time this is indeed the ideal default behavior, but sometimes it would be nice to have a persistent views. it would be nice if we had an optional argument in the read_parquet().
At very least, the read_parquet() documentation should be more precise in stating it creates a temporary view, not a view, not a table, not a temporary table.
What version of ibis are you running?
9.5.0
What backend(s) are you using, if any?
duckdb
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Is your feature request related to a problem?
read_parquet creates only temporary views
What is the motivation behind your request?
I would like to be able to pre-populate a local
duck.dbdatabase with VIEWs that can be accessed by other backends that also use duckdb, without resorting to raw SQL code.Describe the solution you'd like
Most of the time this is indeed the ideal default behavior, but sometimes it would be nice to have a persistent views. it would be nice if we had an optional argument in the read_parquet().
At very least, the read_parquet() documentation should be more precise in stating it creates a temporary view, not a view, not a table, not a temporary table.
What version of ibis are you running?
9.5.0
What backend(s) are you using, if any?
duckdb
Code of Conduct