sql 2025-06-18

Does DuckDB have problems producing qualified maps? I've tried adding :ResultSetMetaDataOptions "1" to my DS but it doesn't seem to make a difference. Is there a way to check at the DB level if the DB is the issue?

https://github.com/duckdb/duckdb-java/blob/main/src/main/java/org/duckdb/DuckDBResultSetMetaData.java#L332 .getTableName() returns "" so you won't get table names on your column keys.

👀 1

Oracle is the same, as I recall.

Clear as day when you know where to look. Is there an idiomatic workaround for this? My guess would be to use rs/as-modified-maps with :qualifier-fn (constantly table-name) or so.

Well, that won't work with JOIN -- on other DBs you'd get the table/column for each joined table, whereas :qualifier-fn applies the same qualifier to all columns.

But with that caveat, yeah, :qualifier-fn gets you part of the way.

Got it. Thank you, @seancorfield.