Relational database? #22
Replies: 6 comments 4 replies
-
The db file might serve as cache for REPL mode. |
Beta Was this translation helpful? Give feedback.
-
Intriguing idea. A ready-made data store with a flexible query language would be nicer than writing one specific for the project. If the plan is to leverage SQL syntax, then whether SQLite will work might depend on its math precision. If a parser is written first, it can be used to populate and test SQLite and other options. |
Beta Was this translation helpful? Give feedback.
-
I actually didn't think of using any database for this. I know rust has many key-value pair libraries which might be beneficial but I want to see the rational for using a database before complicating the parsing and increasing time to render. What I really like about |
Beta Was this translation helpful? Give feedback.
-
It seems that hledger has such integration already implemented and it helps immensely with more complicated reports. Just became aware of this from Simon's answer about specific transfers from account A to account B. https://ledger-rs.github.io/cookbook/transactions-reports.html#specific-transfers |
Beta Was this translation helpful? Give feedback.
-
It is interesting to see the Google Chrome team deprecating the WebSQL and transitioning to SQLite WASM. |
Beta Was this translation helpful? Give feedback.
-
https://www.sqlite.org/fasterthanfs.html "35% Faster Than The Filesystem" |
Beta Was this translation helpful? Give feedback.
-
Is a relational database easier to work with for reporting?
Technically, it would be possible to use an in-memory sqlite database, populated with the data that the parser produces. The text file would be the source and the database only a temporary store.
A temp database file could be used if too much memory is consumed by the in-memory option.
Resources:
Beta Was this translation helpful? Give feedback.
All reactions