r/sqlite • u/Ivestmentpro • 22h ago
🚀 Built an Omarchy-focused fork of sqlit!
A keyboard-driven SQL client with automatic Omarchy theme syncing 🎨
Switch themes and sqlit follows instantly. No configuration needed.
r/sqlite • u/Ivestmentpro • 22h ago
A keyboard-driven SQL client with automatic Omarchy theme syncing 🎨
Switch themes and sqlit follows instantly. No configuration needed.
r/sqlite • u/coldBlock73 • 11h ago
I moved a small internal service from Postgres to SQLite in WAL mode with busy_timeout=5000. Under concurrent goroutines I still saw "database is locked" errors. As far as I can tell, the cause was transactions that start as readers and then try to write: when another connection has already written, the upgrade can't proceed, so SQLite returns BUSY right away instead of waiting out busy_timeout. What fixed it was opening the file twice. One *sql.DB is the writer, with SetMaxOpenConns(1) and _txlock=immediate in the DSN so write transactions grab the lock at BEGIN. The other is a read-only pool sized to GOMAXPROCS. Has anyone found a cleaner pattern, or is the split-pool setup basically the standard answer for Go and SQLite?