Can I attach only to an existing DuckLake?

[arouel]

I stumbled multiple times over the issue that a DuckLake (with PostgreSQL catalog) got newly created, while I was assuming I connect to an existing one. The causing issue is typically some setup problem, but it took me some time until I figured it. So the default "create if not exists" behavior during ATTACH is sometimes impractical. Is there a way to disable the automatic creation of the DuckLake during ATTACH? In other words, is there an option to produce an error when calling ATTACH on a non-existent DuckLake?

[gahtan-syarif]

Have you tried ATTACH IF NOT EXISTS?

[arouel]

It is the opposite of what I want.

[gahtan-syarif]

It is the opposite of what I want.

Then try ATTACH IF EXISTS?

[arouel]

Does not work.

[Mytherin]

I've added support for this in #248

ATTACH 'ducklake:new_ducklake.db' (CREATE_IF_NOT_EXISTS false);
-- Existing DuckLake at metadata catalog "new_ducklake.db" does not exist - and creating a new DuckLake is explicitly disabled

[arouel]

Thank you @Mytherin