Closed michaelmdresser closed 6 months ago
Hmm, if you go build
, and then swap out the duckdb binaries to an older version, I think it also breaks. Same, if you use an older binary of go-duckdb with a newer binary of duckdb. But if you ensure matching versions/binaries, you avoid this issue. There is nothing to address in go-duckdb here, as it does not hard-code the enum values. You can also wait until 0.10.1, which reverts/fixes the issue.
Thanks for the clear explanation! Also, thank you for your contributions to the library; they have been of great help.
Because go-duckdb uses the C library, I'm wondering if it is affected by this issue or if it has already been addressed in go-duckdb: