ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #sqlite
Struggling with read/write conflicts in embedded SQLite? Switching to Write-Ahead Logging (WAL) significantly improves concurrent read performance without sacrificing transactional integrity.
When a K3s cluster loses API access after a node restart, the embedded SQLite etcd datastore is often the hidden cause.
When a simple key‑value store can’t handle your data, Titanium’s Ti.Database and Titanium.Utils give you a lightweight SQLite solution. Learn how to design schemas, perform CRUD operations, and manage migrations while keeping your UI responsive.
Architecture notes for persisting Alloy models to SQLite in Titanium, including schema boundaries, encryption, migrations, and UI-thread checks.
Stop fighting 'Database is Locked' errors in SQLite. Learn how Write-Ahead Logging (WAL) enables concurrent readers and writers to operate without blocking each other.
Use SQLite's INSERT ... ON CONFLICT DO UPDATE to replace SELECT-then-write races with a single idempotent statement, provided a UNIQUE or PRIMARY KEY defines the conflict target.
Architecture note on K3s embedded SQLite for single-node clusters: requirements, minimal design, trust boundaries, operational checks, failure modes, and migration triggers with qualified statements and uncertainty markers.
K3s replaces etcd with SQLite by default, saving memory and operational overhead on edge devices. This post explains why that works, when it breaks, and how to migrate to PostgreSQL for HA — with a concrete step-by-step example.
Learn how to eliminate 'Database is Locked' errors in SQLite by implementing Write-Ahead Logging (WAL) to allow concurrent reads and writes.
k3s
kubernetes
appcelerator