Skip to content

DuckDB fix

DuckDB fix #592