I’ve built and deployed specifically small applications using sqlite and yeah I agree with everything, but especially the migration pains. Any change becomes difficult and bringing another developer onto a project just slows it to a crawl when db changes are needed. If that can be resolved I could be convinced, but until them postgres4lyf
I love SQLite in the command line. Being able to import data sets into a db that I can quickly write queries for has saved me a lot of data processing time.
The CSV import tool is so useful too. I’ll find myself looking at an excel sheet or something and thinking “if only I could query this like SQL”.
In a world of containers and stateless applications, fuck SQLite.
You can always use sqlite cloud
/s?
Please teach me how to configure my containers so SQLite can scale horizontally.
Other databases have the same issue, try having multiple database containers (without massive speed losses). If application is bound by the performance of the front end, this is a problem, but those really are not what SQLite was intended for.
In the case of database bound applications, SQLite is just as good as any other database, which despite having a client server model can typically only handle a single operation at once.
… you know you can put SQLite in a container right? It doesn’t even need to be persisted to disk - it can just live in RAM.
From their “code of ethics”
- First of all, love the Lord God with your whole heart, your whole soul, and your whole strength.
- Deny oneself in order to follow Christ.
- Fulfill not the desires of the flesh; hate your own will.
There are even more strange ones, but I hope you get the picture. Reason enough to use something else if possible.
I would think that’s satire of insanely long and irrelevant rules documents.
Some background: https://www.theregister.com/2018/10/22/sqlite_code_of_conduct/
If you actually read the page, it’s intended as a tongue-in-cheek box-checker.
This document was originally called a “Code of Conduct” and was created for the purpose of filling in a box on “supplier registration” forms submitted to the SQLite developers by some clients.
This document continues to be used for its original purpose - providing a reference to fill in the “code of conduct” box on supplier registration forms.
https://www.theregister.com/2018/10/22/sqlite_code_of_conduct/
They are serious about the religious stuff. And someone who kicks the concept of a code of conduct with their feet like this is surely not a person that is nice to be around.
They are serious about the religious stuff.
I fail to see how that’s an issue.
Also, in the very page you linked, he clarified:
In the face of today’s attention, which has included a wave of aggressive responses accusing Hipp of un-Christian behavior – he tells us he updated the preface to highlight the fact that by adopting St Benedict’s rules he was not seeking to exclude anyone.
“Nobody is excluded from the SQLite community due to biological category or religious creed,” he told us. “The preface to the CoC should make this clear. The only way to get kicked out of the SQLite community is by shouting, flaming, and disrespectful behavior. In 18 years, only one person has ever been banned from the mailing list.”
He also said that he considered only retaining the bullet points that would be relevant to the project, but ultimately decided that would be disrespectful to the original text and its author. Seems fine to me.
Thanks, everyone knows they have a weird coc. It obviously only applies to the maintainers/members of the project though and is more of a statement than something that is actually enforced. As a convinced atheist, I also find it pretty weird but see absolutely no reason at all to avoid sqlite because of that. What matters is: Code quality/correctness (which is absolutely superb when it comes to sqlite) and license, of course. Why would I care about the authors beliefs? They don’t even directly benefit from me using their product.
@words_number @Sibbo that was one hell of an opening sentence to misread.
I love SQLite! My current project actually uses it to serve read-only web content - it’s plenty fast, and it’s really nice having everything baked into the executable. No need to juggle a separate database server.
Their docs are also superb - maybe I’m weird, but I like reading about stuff like atomic commit.
