undefined | Better HN

0 pointsthadt2y ago0 comments

Which, for this use case - bulk generating a read-only data file from a source dataset in a batch job - seems like a pretty good performance tradeoff, no? In the case of a failure of some kind - no big deal, just restart the process anew.

This is one of those use cases where SQLite isn’t replacing <database> - it’s replacing fopen.

0 comments

zylepe2y ago

Exactly, this use case is write-once then read-only after that. Random updates to the sqlite file after that would need more “normal” settings, but they wouldn’t also need as much throughput.

forinti2y ago

It would be nice to have a compendium of SQLite use-cases and their respective configurations.

j / k navigate · click thread line to collapse

0 pointsthadt2y ago0 comments

This is one of those use cases where SQLite isn’t replacing <database> - it’s replacing fopen.

0 comments

zylepe2y ago

Exactly, this use case is write-once then read-only after that. Random updates to the sqlite file after that would need more “normal” settings, but they wouldn’t also need as much throughput.

forinti2y ago

It would be nice to have a compendium of SQLite use-cases and their respective configurations.

j / k navigate · click thread line to collapse