Skip to content

Migrate to SQLDelight #101

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

Open
wants to merge 20 commits into
base: master
Choose a base branch
from
Open

Migrate to SQLDelight #101

wants to merge 20 commits into from

Conversation

antweb
Copy link
Collaborator

@antweb antweb commented Jul 23, 2024

No description provided.

antweb added 20 commits May 7, 2025 14:33
PretixScan.data is no longer needed. This change removes the setup of
the BlockingEntityStore instance and moves the SQLCipher migration logic
to the init code for the SQLDelight database.
The Android driver already handles migrations and schema creation for
us.
To avoid trouble with migrations, it's safer to just re-open
the DB after the cipher migration, so that SQLDelight's on-open hooks
can run properly.
In the previous state, at least some of the initial queries failed,
including at least one `PRAGMA user_version;` query.
Questions are not synced when running against a pretixSCAN proxy.
optString returns "null" for null values, which makes "null" visible in
the UI.
@antweb antweb changed the title Prepare migration to SQLDelight version of libpretixsync Migrate to SQLDelight May 7, 2025
@antweb antweb marked this pull request as ready for review May 7, 2025 13:53
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