Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

all: rename package to github.com/charlievieth/go-sqlite3 #1

Merged
merged 1 commit into from
Nov 26, 2024

Conversation

charlievieth
Copy link
Owner

This project is a hard'ish fork of github.com/mattn/go-sqlite3 that will not always be compatible with the original. Therefore I'm renaming it to avoid confusion.

Regarding incompatibilities, the first is that mattn/go-sqlite3 allows for the SQL passed to Query to contain multiple statements, but will only execute the last one - this package will return an error if Query is passed multiple SQL statements. The second incompatibility is that this library will eventually remove the rarely used RegisterAggregator since it uses reflect.MethodByName which disables dead code removal. The goal is to keep the number of incompatibilities to minimum, unless justified by correctness or performance reasons.

The overall goal of this package is to be more correct and performant than mattn/go-sqlite3 while not being constrained by backwards compatibility (apart from removing RegisterAggregator this package should only introduce breaking changes to code that is already incorrect).

This project is a hard'ish fork of github.com/mattn/go-sqlite3 that will
not always be compatible with the original. Therefore I'm renaming it to
avoid confusion.

Regarding incompatibilities, the first is that mattn/go-sqlite3 allows
for the SQL passed to Query to contain multiple statements, but will
only execute the last one - this package will return an error if
Query is passed multiple SQL statements. The second incompatibility
is that this library will eventually remove the rarely used
RegisterAggregator since it uses reflect.MethodByName which disables
dead code removal. The goal is to keep the number of incompatibilities
to minimum, unless justified by correctness or performance reasons.

The overall goal of this package is to be more correct and performant
than mattn/go-sqlite3 while not being constrained by backwards
compatibility (apart from removing RegisterAggregator this package
should only introduce breaking changes to code that is already
incorrect).
@charlievieth charlievieth merged commit 16597e3 into master Nov 26, 2024
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant