← Graph

Is starting with SQLite a lock-in if I later need Postgres?

question 3 connections

Audience question: if a hobby project grows, can I switch from SQLite to Postgres without pain? Margheim: short answer, no lock-in. SQLite's schema and type system are a looser subset of Postgres's, so going from simple/loose to complex/strict is easier than the reverse. Active Record already abstracts the database — at test.io the team just migrated three apps from MySQL to Postgres thanks to that abstraction. Using the enhanced-sqlite3-adapter gem doesn't bind you either: `bundle remove` leaves no source-file changes behind because it only patches via initializers.

answer_summary
No meaningful lock-in: SQLite types are a subset of Postgres's, Active Record abstracts the DB, and the enhanced-sqlite3-adapter gem patches only via initializers so `bundle remove` cleanly reverts.
question Is starting with SQLite a lock-in if I later need Postgres?
about
PostgreSQL tool
Question asks about migrating away from SQLite to Postgres.
question Is starting with SQLite a lock-in if I later need Postgres?
about
Active Record concept
Answer credits Active Record's database abstraction.
question Is starting with SQLite a lock-in if I later need Postgres?
asked_at
How (and why) to run SQLite in production talk
Q&A after Margheim's talk.

Provenance

Created in
How (and why) to run SQLite in production — Stephen Margh... 2026-04-17 23:20
Read by
7 extractions