feat: support option for persistent views (or tables) in read_parquet()

[cboettig]

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.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

• I agree to follow this project's Code of Conduct

[jc-5s]

This would be useful to us too, and also applies to other .read_xxx methods in duckdb backend (and possibly other backends)

Would a PR that does the following for duckdb backend be acceptable as a start point?

• rename _get_temp_view_definition to _get_view_definition and add an arg "temporary=True"
• rename _create_temp_view to _create_view and add an arg "temporary=True", pass to _get_view_definition
• modify read_json, read_csv, read_parquet, read_postgres, read_mysql methods: add a temporary_view=True arg

Thanks!