Update Kotlin SDK and core extension #83
Open
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.
This makes the Swift SDK compatible with changes from powersync-ja/powersync-kotlin#277 without adding encryption support right away.
We now depend on
CSQLiteto compile and link SQLite statically. That Swift package has a set of default package traits enabling modern SQLite features and recommended compile-time options. That includes passingSQLITE_THREADSAFE=0, which is not appropriate for PowerSync because we use SQLite across threads (just a connection is not used concurrently). It also passesOMIT_AUTOINIT, so we need to manually callsqlite3_initialize()before opening a database.Note: The initial proposal for package traits suggests that passing traits on a package dependency overrides the set of default traits. At least with some poking in XCode compilation logs, that doesn't actually apear to be the case and we can't disable those traits in XCode builds (lol). Enabling the
THREADSAFE_2trait keeps theTHREADSAFE_0trait active, but due to the wayCSQLiteis set up, it happens to override the prior one.