3 ms·
My guess would be that SQLite is great for record/rows but not so good for bulk (de)serialization, as the sibling comment notes. A better flexible format nowada
by adolph 5y ago
My guess would be that SQLite is great for record/rows but not so good for bulk (de)serialization, as the sibling comment notes. A better flexible format nowadays might be Apache Arrow for the task at hand.
Given Joel Spolsky’s stories of weird Excel corner cases the Numbers team had their hands full making redundant software somehow different and yet remain grounded in something akin to printed sheets of paper.
https://www.joelonsoftware.com/2006/06/16/my-first-billg-review/ https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev...
- nerdponx 5y agoIf you don't work with spreadsheets often, you'd be surprised at how often spreadsheets deviate from the strict row/column format. SQLite actually sounds like a bad idea, unless you use it as a key-value store for cells.
- fnord123 5y agosqlite is great for bulk (de)serialization. But it helps if you can setup the queries to pull all the relevant data at once. If you have a deep formula hierarchy it might be difficult to do this naively and get performance. If you're loading an entire sheet, I guarantee sqlite will be faster than deserializing protobuf.