Closed ciupicri closed 1 month ago
It seems to be fixed in duckdb version 1419336e2bc6a71860fb05220927f339375ea8f8 and sqlite_scanner version 50b7870be099186f195bc72bac5e9e11247ee2f9
I'd say this is the same as https://github.com/duckdb/duckdb/issues/12212, basically not all pair DuckDB and sqlite are valid.
Two pairing that are guaranteed to work at a given moment in git history are:
Thanks for raising, documentation / wording can be improved, but it's fundamentally not supported in general.
What happens?
To Reproduce
Compile duckdb version 7ca1d378437718e86d9f2788e5b165bac532e63c with:
Clone sqlite_scanner version d355dd0b072653590e1d8c0d83501f4b20358694, symlink to the previous duckdb repository then compile with:
I'm using __gcc-c++-14.1.1-1.fc40.x86_64__
OS:
Linux x64 (Fedora 40)
SQLite Version:
3.45.1-2.fc40.x86_64
DuckDB Version:
7ca1d378437718e86d9f2788e5b165bac532e63c
DuckDB Client:
7ca1d378437718e86d9f2788e5b165bac532e63c
Full Name:
-
Affiliation:
-
Have you tried this on the latest
main
branch?Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?