Downgrade sqlite3 and apsw to 3.6.22(-r1) #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 0592915.
… files because otherwise we get IO errors
|
Tested with taking apsw in the distribute script. Everything still works. |
rjagerman
added a commit
that referenced
this pull request
May 21, 2014
Downgrade sqlite3 and apsw to 3.6.22(-r1) Tested and works!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Even though the sqlite3 file included in p4a (
src/jni/sqlite3/sqlite3.c) is a big cluster fuck (4 year old fork that has 2200+ lines different from the official sqlite v3.6.22 it claims to be and even has an unresolved merge conflict), it seems more reliable than the standard/updated sqlite version from #3 and it seems to be the only way to get the apsw package working (only way to avoid IO errors).