-
Notifications
You must be signed in to change notification settings - Fork 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
Moving from quick sqlite to the new op-sqlite #42
Comments
Btw, i just found this post: |
As shown by those benchmarks, for most use cases the performance difference between the various options is not massive. There is a bit of gain in using JSI, which is the case for both op-sqlite and react-native-quick-sqlite. For general react-native use cases, I'd recommend op-sqlite. Our fork of react-native-quick-sqlite here is generally to:
We'll likely move PowerSync over to op-sqlite in the future, since it seems like we'll be able to support all those without maintaining a separate fork. |
hi @rkistner , i hope the move over will be process as soon as possible. |
Yes, we expect performance to be the same or perhaps slightly better on op-sqlite. |
hi @rkistner , i mean when i use old version sqlite of Powersync, then later when upgrade Powersync using new version (op-sqlite), does everything in our user mobile app will be work the same? Thanks |
Yes, it will continue using the same database file, and the PowerSync APIs will remain the same |
Also in favor of this move to help support running with the new architecture |
Hi powersync team, op-sqlite is much faster and active maintain from the author.
I just want to ask, does it support underly by Powersync right now? or you are using quick-sqlite to decide to try Powersync.
Thanks
The text was updated successfully, but these errors were encountered: