[dead]
SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers
81–87 of 87 posts
Re: SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers
#82Earlier quoted context omitted.
Even your comment looks like it's generated by AI.
"You must accept the truth from whatever source it comes." - Maimonides I feel like "this is AI" needs to join the ranks "it's not that deep" and "this is a Wendy's" as an annoying thought-terminating cliche.
except 99% of AI—written content is spam. If the article was an ad for some company and also made no sense, would you hate on the guy who commented "this is an ad"?
Re: SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers
#83Earlier quoted context omitted.
"You must accept the truth from whatever source it comes." - Maimonides I feel like "this is AI" needs to join the ranks "it's not that deep" and "this is a Wendy's" as an annoying thought-terminating cliche.
except 99% of AI—written content is spam. If the article was an ad for some company and also made no sense, would you hate on the guy who commented "this is an ad"?
Because that's not what happened? What? Neither smartmic's root-level comment or rdsubhas's response mention it being an ad. I was criticising adhamsalama's dismissal of rdsubhas's comment as AI, who also said nothing about it being an ad. I'm so baffled. Can you not see the structure or the content of this thread?
Re: SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers
#84Earlier quoted context omitted.
You create a nullable column and then change it to not null. Which wasn't possible in SQLite until recently.
I’m not sure what your original point is pointing out . Some data doesn’t convert is what I’m pointing out regardless of Postgres or SQLite.
Ah, my bad, first I was wrong about null/not null, and now I see what you mean.
Re: SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers
#85[dead]
Re: SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers
#86Earlier quoted context omitted.
except 99% of AI—written content is spam. If the article was an ad for some company and also made no sense, would you hate on the guy who commented "this is an ad"?
Because that's not what happened? What? Neither smartmic's root-level comment or rdsubhas's response mention it being an ad. I was criticising adhamsalama's dismissal of rdsubhas's comment as AI, who also said nothing about it being an ad. I'm so baffled. Can you not see the structure or the content of this thread?
did you actually read my comment
Re: SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers
#87Earlier quoted context omitted.
I have to disagree with this as off topic. The blog lists ways to optimize sqlite for production, for those who have already made that choice. But these comment links are about choosing sqlite vs others and differences, which is completely unrelated and unnecessary for those who have already made that choice. I'm seeing a worrying trend on HN. Nearly for all articles, there is one unquantified, unproven comment at th…
I'm more than aware that my comment won't move the needle on the AI debate a slight bit, but I do think that the readership deserves some honesty and transparency there. No, not a single LLM ever has "deployed SQLite in Production", had to be on duty during the weekend, had to pop open a terminal to a misbehaving service while on family vacation, nor meaningfully suffer the anguish and stress to hotfix a botched or m…
I'm on-call all the time, and the first thing I've taught myself is to not glorify it like some superhero saves the day worship. I'm both proud and (slightly) ashamed each time I handle an incident. It's not a virtue.
How many people who were writing blogs or creating open source tools before signed an on-call oath or declaration? Does that mean they're all wrong or unqualified?
On call avoidance should be rewarded more than on call superheroism. People managing software fail to realize it. Avoidance is stashing enough operational bullet points, mental checklists and manpages.
Everything is generic — because your use case and your operating environment is ONLY yours. Postgres has hundreds of parameters. Nothing is specific or made to satisfy you. If it doesn't, then you don't call the parameter as generic. You choose what to apply for your environment and expectation.
What you're saying is both a wrong reward cycle and it was also not necessary or practical before AI.