I've upgraded/downgraded the go-sqlite3 package to the v1 branch. This seems weird, but the maintainer of the go-sqlite3 package made the v2.* versions accidentally. (See https://github.com/mattn/go-sqlite3/blob/master/README.md)
The github.com/wader/gormstore/v2 package also depended on this v2.* branch of the go-sqlite3 package, but was fixed in v2.0.1.
The v2.0.3 version of go-sqlite3 is old and has some problems, which are fixed in later v1.* versions.
The v0.0.5 version of this package makes it unable to use the newer v1.* versions of go-sqlite3. I had to downgrade to v0.0.4 to be able to do so. This PR should fix that problem.
LGTM
I agree with @DemonTPx say.
The latest of https://github.com/mattn/go-sqlite3 package is v1.14.15.
The v2.* versions of go-sqlite3 just come from an accident.
Hi,
I've upgraded/downgraded the go-sqlite3 package to the v1 branch. This seems weird, but the maintainer of the go-sqlite3 package made the v2.* versions accidentally. (See https://github.com/mattn/go-sqlite3/blob/master/README.md)
The github.com/wader/gormstore/v2 package also depended on this v2.* branch of the go-sqlite3 package, but was fixed in v2.0.1.
The v2.0.3 version of go-sqlite3 is old and has some problems, which are fixed in later v1.* versions.
The v0.0.5 version of this package makes it unable to use the newer v1.* versions of go-sqlite3. I had to downgrade to v0.0.4 to be able to do so. This PR should fix that problem.
Thanks, Bert