-
Notifications
You must be signed in to change notification settings - Fork 27
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
SQLite Support #50
Comments
Putting this as a reply as not to muddle the proposal post. I can try to fit in time in my schedule to add this functionality myself. I would need to know the requirements to have a pull request accepted. |
Hi Antonio, |
Closing as a stale issue. I'm definitely open to SQLite support and will review PRs, but I don't have need for it myself so it's not on the current roadmap. |
Hello,
I understand that the JSON file support offers a nice "on file database" solution, but I would like to propose offering SQLite support as well. JSON Files have a locking issue, and are limited by the file system. SQLite 3 offers most of the power of PostgreSql with the advantages of being lighter weight in every way. Along with offering a single easy to backup file as opposed to a complex database system that requires dedicated backup tools. SQLite is also a popular developer alternative to PostgresSql, as it allows the developer to reduce load on their machine while developing.
SQLite recently added support for json fields which should allow for a fork of "mongo-query-to-postgres-jsonb" that turns it into "mongo-query-to-sqlite-json1".
The text was updated successfully, but these errors were encountered: