3 ms·
Not sure why this got posted when the follow-up claws back much of it and leaves a pretty weak conclusion: https://www.hendrik-erz.de/post/should-you-use-sqlite
by k8svet 3y ago
Not sure why this got posted when the follow-up claws back much of it and leaves a pretty weak conclusion: https://www.hendrik-erz.de/post/should-you-use-sqlite https://www.hendrik-erz.de/post/should-you-use-sqlite
- cchance 3y agoYa was gonna say the first thing i saw was basically a "correction" post and then you read that and hit "The actual reason why I think you shouldn’t use SQLite is one of time constraints: Implementing a layer of SQLite will probably take you more time than simply to reduce the amount of files. " Like no i'm sorry implementing a SQLite layer, vs implementing a filesystem layer is the same time or faster. I mean seriously he thinks trying to negotiate how to stop having 600,000 files is easier than just... ummm... using standard sql?