Open deepyaman opened 2 weeks ago
This does seem like a potential footgun.
I think with DuckDB, at least, read parquet wouldn't overwrite an existing table, but read_parquet is creating views and we're likely doing a create or replace
.
I think an overwrite kwarg is a good idea
Just to spell this out concretely:
There should be an overwrite
kwarg to read_parquet
(and read_csv
, read_json
, etc...) that defaults to False
.
In terms of creating tables / views, we should default to CREATE VIEW name AS ...
and only throw in a CREATE OR REPLACE
if overwrite=True
What happened?
Here's an example derived from a user issue:
Shouldn't
read_parquet
, etc. just have an overwrite option? If you don't specify that, it should not let you clobber an existing table.What version of ibis are you using?
9.0.0 (initially reported on 8.0.0)
What backend(s) are you using, if any?
DuckDB, but can be replicated on other backends
Relevant log output
No response
Code of Conduct