Sorry, wasn't meaning to be rude but the title of the post implied there was some insights being shared. Instead, it was telling us that SQLite has WAL mode, and that it should be used.
There was nothing there that actually talked about issues or lessons from working with it.
I'm copying out 2 points I think are most relevant here:
- Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community.
- Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
I asked for counter-proof of my dismissal and reasoning, and all you offer up is copy pasted points that aren't applicable.
Yes my dismissal was shallow, as was the article in question. Here's a more verbose version that should satisfy you?
The article speaks of using SQLite in production but only mentions the existence of WAL-mode and suggests its use. That is general (not production specific) advice that is well known in the community. While the promotion of SQLite is a good thing, I found this article wanting in delivering on what the title suggested.
There was nothing there that actually talked about issues or lessons from working with it.
What did that post tell us about that this one doesn't: https://sqlite.org/wal.html
Edit: instead of drive-by downvotes, what about giving me a counter example that shows that the article is worthy of being on the front page of HN?