DuckDB: Workspace db is Empty, Local Path Works

I am exploring the use of DuckDB within KNIME. The experience was pretty straight forward:

• Created a custom Database Driver using the DuckDB Jar

• I can connect to a file on my machine via `jdbc:duckdb:/Users/<me>/<path>/<class>/sessions2024/10-db/music.duckdb`

• The reader node can successfully list the tables in this simple database via a SQL query

Instead of having students reference a full path on their machine, I was hoping that I could drop the folder into the Project Workspace to simplify the path.

• `jdbc:duckdb:music.duckdb` can recognize the file in the DB Connection node

• The same query does not return any data via Reader

My long winded question: Why is that a fully qualified path for the same database works as expected, but when I drop the file into the workspace, a shorter, easier path does not?

Context: I am hoping to simplify the process of connecting to a duckdb database file as much as possible for my upcoming class this spring. File paths will be a point of friction for this set of students.