Skip to content
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

Add a long lasting db solution #117

Open
dennyweiss opened this issue May 12, 2023 · 2 comments
Open

Add a long lasting db solution #117

dennyweiss opened this issue May 12, 2023 · 2 comments

Comments

@dennyweiss
Copy link

Querying data in a db way got much better with proper pagination (#116 ) and non key based property (#108). 🙏🏽
Why not target a long-lasting solution in the form of SQLite or some key value DB's

see:

  1. ICSQLite
  2. IndexedDB
  3. dino
@dennyweiss dennyweiss changed the title Add SQLite as db Add a long lasting db solution May 12, 2023
@peterpeterparker
Copy link
Contributor

Great to hear that these improvements are helpful!

In the long term, my plan is to introduce more advanced forms of satellites with e.g. enhanced scalability capabilities.
Additionally, I aim to offer more sophisticated database options such as improved SQL or other alternatives as you are mentionning. This is what I mean with the "Templates Store" section of Juno's roadmap.

On the short term, I believe that the simplicity of the current datastore allows for the development of various application concepts. It offers the advantage of being tightly encapsulated without relying on additional services. Based on my experience, it's also beneficial to start a project with less reliance on third-party software.

Thank you for sharing those valuable links, they align perfectly with the vision for the future!

@peterpeterparker
Copy link
Contributor

  1. ICSQLite is currently incompatible with wasm32-unknown-unknown Can't build for wasm target rusqlite/rusqlite#827.
  2. IndexedDB works only in the browser therefore not an option.
  3. dino is deprecated or at least inactive since 4 years, therefore it is probably not a valid option.

i.e. there isn't a solution at the moment.

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

No branches or pull requests

2 participants