You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using requery since version 3.4.6, my conclusion is that the drawbacks outweigh the benefits.
The benefit is to be able to use newer sqlite features on all API levels:
JSON support (not available on any Android version yet). We use this at the moment for returning the list of tags together with the main transaction list query.
Windowing functions (available only from Android 11). These are not used at the moment, but are planned to be used in implementation of Running balances #239
Since we changed the way we instantiate the database, we also see reports about race conditions during startup (unfortunately not reproducible on our side) that might not occur with FrameworkSQLiteOpenHelperFactory.
The text was updated successfully, but these errors were encountered:
Using requery since version 3.4.6, my conclusion is that the drawbacks outweigh the benefits.
The benefit is to be able to use newer sqlite features on all API levels:
The drawbacks:
Since we changed the way we instantiate the database, we also see reports about race conditions during startup (unfortunately not reproducible on our side) that might not occur with FrameworkSQLiteOpenHelperFactory.
The text was updated successfully, but these errors were encountered: