Documentation for COPY TO: Please mention there is no need for overwrite guard code about duckdb HOT 4 OPEN

The file is not corrupted, it's simply not in parquet format because how could duckdb possibly know that you wanted it in parquet format? You need to add (FORMAT PARQUET) to your COPY statement if you want to write a parquet file but don't want to use a parquet file ending.

As to duckdb getting this right automatically: personally I'd be more surprised if it didn't, but feel free to make a PR at the documentation repository (note that each page of the documentation website has a link at the bottom to the corresponding source in GitHub, e.g. https://duckdb.org/docs/sql/statements/copy.html links to https://github.com/duckdb/duckdb-web/edit/main/docs/sql/statements/copy.md)

from duckdb.

The file is not corrupted, it's simply not in parquet format because how could duckdb possibly know that you wanted it in parquet format? You need to add (FORMAT PARQUET) to your COPY statement if you want to write a parquet file but don't want to use a parquet file ending.

Thanks, I had forgot about this FORMAT statement, feeling stupid now...

As to duckdb getting this right automatically: personally I'd be more surprised if it didn't, but feel free to make a PR at the documentation repository (note that each page of the documentation website has a link at the bottom to the corresponding source in GitHub, e.g. https://duckdb.org/docs/sql/statements/copy.html links to https://github.com/duckdb/duckdb-web/edit/main/docs/sql/statements/copy.md)

Thanks, I like this feature but it feels like this kind of guard code should always be under the responsibility of the user. But now I know it's not required when working with duckdb :)

from duckdb.

It's not required in this instance. It might fail in more complex problems, and I agree with you that it's bad practice to overwrite an input file, especially when using a declarative system like duckdb.

from duckdb.

Oooof, so I guess I should remove my pull request...

Really thought it was an actual feature

from duckdb.