-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
General development suggestions #62
Comments
Thanks for all the input! I'm going to try improve the codebase and implement most of this in the next weeks! 🚀 We might plan on doing a greater API redesign anyway, so some of these points might already be covered by other changes |
💯 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Responding to #55 (comment), since bloating that PR with extra hopes and dreams wouldn't be productive.
W.r.t. Concurrency. It would be nice to be able to have a read only connection pool and the one connection (or another connection pool) for writing. This could be a huge performance win for more complex application that has heavy database usage.
Having studied this code base (and having had my own, long abandoned venture to alternative, sqlite-jsi), I have some idea of the effort required to implement these things. While I dont have the time / resources to work on this myself (nor am I expecting anyone to do the work either!), if someone is up for the task I am more than happy to chat about the ideas / design / implementation details.
As the sqlite-jsi repo might suggest, I have interest in having a solid sqlite library for react-native - I just lack the time to work on it.
The text was updated successfully, but these errors were encountered: