ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #sqlite
Goal: Use Expo‑SQLite’s executeSql with LIMIT and OFFSET to paginate a local table while another process may insert or delete rows. Constraint: The module forwards raw SQL to SQLite without providing snapshot isolation, so OFFSET values are calculated on the live table state. Uncertainty: It is unclear whether concurrent modifications cause page boundaries t
I'm building an Alloy screen backed by a Backbone collection using the local SQLite adapter. The table will hold several thousand rows, and the target devices have limited RAM, so I need to decide how to bound the query before wiring up data-binding. As I understand it, the collection's fetch ultimately runs SQL through the adapter, so I can pass limit/offse
k3s embedded SQLite datastore constraint for multi‑node high availability The goal is to run a k3s control plane with at least two server nodes so that the API server remains available if one node fails. In a default single‑node installation k3s stores its data in an embedded SQLite file on the local disk, which works for development but does not allow concu
Goal: Use an in‑memory SQLite database together with Prisma’s preview referentialIntegrity feature so that integration tests enforce foreign‑key constraints identical to a production PostgreSQL instance while keeping credentials out of the test environment. Constraint: The referentialIntegrity preview is experimental and its implementation relies on SQLite P
The goal is to guarantee that a prepared statement binding many parameters (e.g., a large IN list) succeeds or fails identically on every developer workstation, preventing the “too many SQL variables” error that appears only on builds with the older default limit. SQLite’s SQLITE_MAX_VARIABLE_NUMBER default changed from 999 to 32766 starting with version 3.3
Choosing WAL vs Rollback Journal for High‑Frequency Small Transactions The application needs a multi‑threaded SQLite database that serves many concurrent read connections while handling a high rate of small write transactions. Rollback Journal mode forces an exclusive lock on writes, blocking all readers until commit, whereas WAL mode permits concurrent read
expo
k3s
prisma