SQLite concurrency and why you should care about it

https://jellyfin.org/posts/SQLite-locking/

#HackerNews #SQLite #Concurrency #SQLite #Performance #Database #Management #Tech #Insights

Why Is SQLite Coded In C

https://www.sqlite.org/whyc.html

#sqlite #c #opensource

What if Django had an automatic ORM feature matrix — showing which features each database really supports, straight from the code? 🧩

I’ve shared some ideas (with demo data!) on how it could work and why it’d be great for Django’s docs 💡

https://www.paulox.net/2025/10/06/django-orm-comparison/

CC @django

#Django #Python #ORM #OpenSource #Database #PostgreSQL #SQLite #MariaDB #MySQL

What if Django had an automatic ORM feature matrix — showing which features each database really supports, straight from the code? 🧩

I’ve shared some ideas (with demo data!) on how it could work and why it’d be great for Django’s docs 💡

https://www.paulox.net/2025/10/06/django-orm-comparison/

CC @django

#Django #Python #ORM #OpenSource #Database #PostgreSQL #SQLite #MariaDB #MySQL

ok chat

what are some _disadvantages_ of #DuckDB compared to #SQLite?

How utterly chaotic is it to build an #Eleventy project backed by a #SQLite database?

How utterly chaotic is it to build an #Eleventy project backed by a #SQLite database?

It’s been a long time since I wrote a blog post rather than a talk - but in architecting Fermyon Wasm Functions and our Wasm platforms to run “anywhere” - I spent a lot of time thinking about “minimal” platform footprints… and made some interesting discoveries. Mostly that #SQLite is still pretty awesome.

https://www.fermyon.com/blog/sqlite-is-edge-scale

It’s been a long time since I wrote a blog post rather than a talk - but in architecting Fermyon Wasm Functions and our Wasm platforms to run “anywhere” - I spent a lot of time thinking about “minimal” platform footprints… and made some interesting discoveries. Mostly that #SQLite is still pretty awesome.

https://www.fermyon.com/blog/sqlite-is-edge-scale

Simple tech stacks are great for resilient and maintainable systems. Why reach for #Valkey / #Redis when you can avoid introducing another dependency by implementing caching with #SQLite triggers?

This was a fun #WebDev experiment and made me even more impressed with how capable this database is for mid-sized websites and apps.

What's your favourite example of #Minimalist#Tech?

https://samuelplumppu.se/blog/using-sqlite-triggers-to-boost-performance-of-select-count

We are VERY excited about all the features landing in the next release! However, we’re also introducing one big breaking change—and that’s the purpose of this post. WE ENCOURAGE EVERYONE USING BADGEFED TO CREATE A DATABASE BACKUP BEFORE UPGRADING.

(GO, do it now, we will wait for you and then continue reading this post.)

Don’t worry: if you forget, chances are you won’t lose data, but recovery may be trickier. If you can, please back up first.

Summary (read before upgrading)

• Database filenames now match your domain, for example: mydomain.db. The previous single default filename is no longer used by default.
• Back up your existing SQLite file NOW. You can also download a backup from the admin portal: Admin > Database > Download Backup.
• After upgrading to 0.1.1, the app uses a per-domain database. Use the import utility to migrate from your backup—or copy your backup into the data directory and rename it to the domain-based filename.
• Prefer one shared database? Set the environment variable SQLITE_DB_PATH to your desired (or current) filename (for example, badgefed.db).

If you already upgraded without preparing

• Your previous database was not replaced or deleted. Locate your old badgefed.db (or backup), copy it to the data directory, and rename it to the new domain-based filename.

The 0.1.1 release and full release notes are coming soon!

Badge up!

You can read the article "BadgeFed 0.1.1 — Breaking change: per-domain database filenames" by @mapachehere as well.

Hey Fediverse! 👋

We’ve been quiet… but not idle. Forget waiting for long blog posts, time for micro updates.

Today’s news:

We’ve got a few BadgeFed instances live and federating! 🏅

To make it happen, we did a hardcore backend rewrite to support multiple domains on a single machine.
For most, it’s a niche cost-saving move, but it might be useful for others too. Under the hood: each domain runs its own SQLite DB, with backups in place.

But this isn’t just about the tech, the fun part is seeing multiple BadgeFed servers talking to each other (!!). Follow them, check the thread, boost it, and watch for more as they come online!

You can read the article "BadgeFed Update: Multiple Instances Online!" by @mapachehere as well.

Hey Fediverse! 👋

We’ve been quiet… but not idle. Forget waiting for long blog posts, time for micro updates.

Today’s news:

We’ve got a few BadgeFed instances live and federating! 🏅

To make it happen, we did a hardcore backend rewrite to support multiple domains on a single machine.
For most, it’s a niche cost-saving move, but it might be useful for others too. Under the hood: each domain runs its own SQLite DB, with backups in place.

But this isn’t just about the tech, the fun part is seeing multiple BadgeFed servers talking to each other (!!). Follow them, check the thread, boost it, and watch for more as they come online!

You can read the article "BadgeFed Update: Multiple Instances Online!" by @mapachehere as well.

rust-query, a library with a better API to query #SQLite databases with #Rust

https://nlnet.nl/project/rust-query/

While that sounds relatively mundane, it's something I'm excited about because Rust really doesn't have as many options as, say, Python, where I just define a model in the code and it automagically generates tables, migrations, and everything in between. Did I say doesn't have options? Well, that was only until now 😉

#RustQuery

🧵 3/n

Alright, folks, who can make a case for using SQLite in production for small hobby sites?

The idea sounds silly to me, but I've been conditioned to consider it solely as a development tool.

Now I wonder: Does this attitude do SQLite dirty?

#SQLite