Repository navigation
v0.1.1
This release fixes one bug and documents a crash that is not a fault of odbc.
Fixed
A statement that returns no result set, such as CREATE TABLE, sent through QueryContext, failed on the first Next with fetching: return code -1 with no diagnostic. The driver fetched from a statement that has no result. It now returns no rows, and Err and Close report no error. A client that sends every statement through QueryContext, as usql can, met this. TestQueryWithoutResult covers all six tested databases.
Documented
- The README has a FAQ entry for a crash of a program that links both
go-sqlite3and the DuckDB bindings and uses the SQLite ODBC driver. The DuckDB bindings link with-rdynamic, so the program exports thesqlite3_*functions ofgo-sqlite3, and the SQLite ODBC driver binds to them while it also uses the SQLite of the system. The first query then faults. Buildgo-sqlite3with the taglibsqlite3, leave one of the two libraries out, or build withCGO_ENABLED=0.odbccannot prevent it. - The SQLite ODBC driver answers a
VALUESstatement withSQL_NO_DATA, so the driver manager refuses to describe its columns withHY010.select * from (values (1))works. The backlog records it as a known limit.
Everything else in v0.1.0 is unchanged, and CI passed on all three systems for this release.