SQLite is all you need for durable workflows

Post by [deleted] » Fri, May 29, 2026, 11:52 PM UTC

simonw wrote: post #157

pseudalopex wrote: post #133

Earlier quoted context omitted.

This could enforce dates are strings. They wanted to enforce dates are dates I thought.

create table events ( id integer primary key, name text not null, event_date text not null check ( -- YYYY-MM-DD event_date glob '[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]' and date(event_date) is not null and date(event_date) = event_date ) ); In Python that raises this error if the date is invalid: sqlite3.IntegrityError: CHECK constraint failed: event_date glob '[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]'

Post by not_kurt_godel » Sat, May 30, 2026, 12:01 AM UTC

tasuki wrote: post #112

ai_fry_ur_brain wrote: post #60

Earlier quoted context omitted.

I use postgres for very simple apps. I have a Dockerfile I use in my boilerplate repo. It takes a single make cmd for me to build, start and run migrations. Its as simple as using sqlite.

But now you have another process to babysit. How do you keep it healthy? And you have to ensure the client-server communication won't break. For me the main benefit of sqlite is that it's a library rather than an app.

Post by rsalus » Sat, May 30, 2026, 12:20 AM UTC

phamilton wrote: post #63

jawns wrote: post #9

Earlier quoted context omitted.

Could you give an example of a case where you'd use SQLite instead of jq or grep through Markdown?

My favorite lens on SQLite is that it is actually two things: 1. A robust durability implementation 2. A library of high performance data structure and algorithms The fact this it's SQL is nice, but those two attributes are what make it great. For example, I'm implement an in-process event log that I want to be durable. I started simple, but soon saw some edge cases and instead of playing whackamole I just swapped to…

Post by pseudalopex » Sat, May 30, 2026, 12:27 AM UTC

simonw wrote: post #157

pseudalopex wrote: post #133

Earlier quoted context omitted.

This could enforce dates are strings. They wanted to enforce dates are dates I thought.

create table events ( id integer primary key, name text not null, event_date text not null check ( -- YYYY-MM-DD event_date glob '[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]' and date(event_date) is not null and date(event_date) = event_date ) ); In Python that raises this error if the date is invalid: sqlite3.IntegrityError: CHECK constraint failed: event_date glob '[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]'

Post by ai_fry_ur_brain » Sat, May 30, 2026, 12:33 AM UTC

not_kurt_godel wrote: post #193

tasuki wrote: post #112

Earlier quoted context omitted.

But now you have another process to babysit. How do you keep it healthy? And you have to ensure the client-server communication won't break. For me the main benefit of sqlite is that it's a library rather than an app.

> But now you have another process to babysit. How do you keep it healthy? I've been assured by many HN users that running apps/sites on a single VPS requires near-zero maintenance or monitoring to achieve acceptable uptime 24/7/365 for years on end, sooooo...just pretend it will never fail like your main server process?