Mark

Thanks for the report! This is a restriction of the `azure` extension. We are planning to implement this in the future - there's an issue that tracks this there: https://github.com/duckdb/duckdb-azure/issues/44...

Thanks for the report! Identifiers should be unique globally, i.e. if a given `id` refers to a view it should not also refer to a table. We could improve the...

All that is required is that a database extension is added, e.g. an extension similar to the Postgres/SQLite extensions. That extension needs to have support for a number of different...

Thanks for the report! Oprhaned files are inevitable if insertions are cancelled before interacting with the catalog. We plan to add a method to remove orphaned files in the near...

Yes, the idea is to do this using schemas

As mentioned you can already store multiple DuckLakes in the same catalog database using the `METADATA_SCHEMA` parameter. This works with back-ends that support schemas - i.e. it works with DuckDB/Postgres,...

Thanks for the suggestion - we are planning to add support for arbitrary write-time default values in the future. The main concern is that arbitrary expressions/function calls are not portable...

Thanks for the report! This seems like expected behavior to me. Data file ids are sequentially assigned, so concurrent writers can encounter primary key constraints there. The retry will then...

Thanks for the PR! Is there a particular issue that this is solving - or is this just picking up a random FIXME in the code? I'm not opposed to...

Thanks for the clarification - adding the SQL function in a follow-up makes sense to me. Could you just add some more tests then, there are a number of edge...