-
Notifications
You must be signed in to change notification settings - Fork 8
Keep up with upstream #2
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
Conversation
This change could save users from having to dig into source code to see how connection options are parsed.
with comments what const are used for what
implementation of set_authorizer interface
Fix build
CryptEncoder SHA384 and SHA512 variants (with and without salt) were incorrectly documented as using SHA256.
Mention correct algorithm in function docs.
Upgrade to SQLite 3.25.0
Fix build
Actually check the value of RunTests
upgrade amalgamation code
Fix typo in README.md
Add Go 1.11 to Travis build matrix
Remove extra backtick and fix Markdown formatting
Update README: URL-encode connection options
Fix gometalinter issues
Clean up blob to byte slice conversion
Distinguish between NULL and zero-length blobs on query
Fix data race in AutoCommit()
Close db even if sqlite3_open_v2 return non-zero.
SQLITE_OPEN_CREATE should be specified for sqlite3_open_v2 if mode is…
… mode is not rw" This reverts commit 03b96a5.
Revert 671
upgrade amalgamation code
s/an/a/
Fix typo in README
As opposed to []byte arrays. This brings sqlite closer in line with other dbs like postgres, allowing downstream consumers to assume the scanned value is string across underlying dbs.
Unify travis runs
@auxten I see these issues
on fresh update from mattn. Do you plan on updating the fork soon? Thanks. Btw, |
Fix typo
hey, thanks for using it 😄 |
No description provided.