You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a usability gap with using DuckLake with JDBC, when a
connection must be opened first and then the following statement must
be executed:
```
ATTACH 'ducklake:...'
```
Executing this additional `ATTACH` step, when accessing DuckLake from
GUI tools or from high-level engines like Spark, is cumbersome and may
require non-trivial configuration.
This change adds two new connection properties:
1. `ducklake`: the `database-path` parameter to pass to
`ATTACH '<database-path>'`.
Value examples:
```
/path/to/lake1.db
sqlite:/path/to/lake1.db
postgres:postgresql://user:[email protected]:5432/lake1
```
If `ducklake:` prefix to the value of this option is not specified - it
is added automatically.
Before running the `ATTACH` it also runs:
```
INSTALL ducklake
LOAD ducklake
```
2. `ducklake_alias`: the `database-alias` parameter to pass to
`ATTACH '<database-path>' AS <database-alias>`.
This is to allow to override auto-detected DuckLake catalog name in
cases when `database-path` has long naming or include UUIDs.
After the connection is established it also runs `USE <database-alias>`.
Testing: test coverage is pending, DuckLake extension is not yet
available in the `main` branch.
0 commit comments