It's in SQLite's documentation, and almost no one switching to Sqlite seems to be aware of it because no one discusses it in blog posts like these. I guess most projects switching to SQLite have very low traffic and no malicious users (yet)

Sometimes (maybe 5% or less) the request won't render at all, and you get a browser error page.

Today they ran into this bug, lost a bunch of voting data, and went into read-only mode for several hours:

https://github.com/rails/rails/pull/57128

I wonder how much of this is usual bugs which crop up during major database migrations, and how much is caused by choice of SQLite.

K1 acquired the commercial entity behind MariaDB Enterprise, but that's separate from the non-profit MariaDB Foundation. And there's literally zero risk of the MariaDB server suddenly going closed-source; as a fork of MySQL (which is GPL), this is not even legally possible!

[1] https://github.com/lobsters/lobsters/issues/539#issuecomment...

1. Stats are used by "Cost-Based Optimizers."

I think this is the most appropriate wiki:

https://en.wikipedia.org/wiki/Query_optimization

On my Oracle databases, I run the dbms_stats.gather_database_stats package procedure once a week. SQL Server also has stats for sure, and I would be surprised by a relational database that did not.

SQLite will quietly gather stats with each database connection. Running an explicit analyze devotes full attention to an otherwise piecemeal group effort.

2. I don't think rows are physically removed when deleted, instead they are marked. Removal will definitely happen at vacuum.

3. There is a backup command in the CLI that will make a transaction consistent copy of the database file, and there are lower-level C functions behind it that can be used with object code.

4. It is important to remember the many restrictions of WAL mode, including the impact on ATTACHing multiple database files: ACID consistency is lost.

https://sqlite.org/lang_attach.html

'Transactions involving multiple attached databases are atomic, assuming that the main database is not ":memory:" and the journal_mode is not WAL.'

In any case I will take an invite if one has one because the community is solid.

https://lobste.rs/s/ko1ji1/lobste_rs_is_now_running_on_sqlit...

I hope they get it sorted soon, I'm rooting for sqlite.

make sure you're not doing a bunch of migrations. that's the SQLite weak point that I know of & have experienced.

use SQLite - as if you're using a KV or better yet maybe a CQRS approach.

https://sqlite.org/rsync.html

... and is installed and available:

  # sqlite3_rsync -vv ./test.db user@rsync.net:test.db

I'm not interested in a rehash of Hacker News but I am interested in more tech news.

Anyhow on topic: I find it puzzling the whole "use sqlite in production!" thing.

- you're stuck on a single machine now.

- you don't have remote database access.

- you have to live with the inflexibility of sqlite's schema change capability.

- all writes go through a single writer.

- fewer data types

- fewer backup/security/high availability options

- foreign keys and strict disabled by default.

- you're single core in a multi core world.

It's not a terrible decision but when you can choose Postgres, why would you go with sqlite?

I do have to say that I've found lobste.rs generally a pretty slow site to render and navigate and I wonder whether that's the Rails backend, or underpowered hardware, or lack of caching. It's more feature-ful than a HN or Reddit though with much lower usage so I wonder what it is.

DHH has made a big deal about using SQLite in rails

That's not necessarily a bad thing, but honestly, as a foreigner, I have limited English vocabulary, so I end up getting stressed out over being judged as AI. At least here, the admin DEN kindly understood my situation and let me participate after getting permission. But when I look at subreddits and other communities, the stronger the monocultural management, the more fan-like sentiment tends to grow, making it harder for minority voices to speak up.

I'm in favor of LLMs (since being for or against LLMs inevitably depends on regional context—I personally find LLM translation incredibly convenient and helpful), but there are moments when I find it hard to argue against blanket opposition or certain topics. I thought about why that is, and I think it's because Lobste.rs has high-quality posts, but since it's inviet only, the cultural barrier to entry is high, and judgment itself is part of the community identity. It's more about signals like 'are you the same kind of person as us' than logical counterarguments. The community is small, so the same core users appear across many topics, and the reputation built there follows you around, making it closed off to minority opinions.

HN, on the other hand, isn't really a single community but a mix of many groups—startup founders, big-tech engineers, and independent developers like me. Depending on who happens to be reading at that time, the comment sentiment often shifts. And since there are so many readers, even if I say something on one thread, it's unlikely anyone will recognize me in the next.

So Lobste.rs feels like a hard place for an outsider to fit into.