better-sqlite3

Used the existing embedded database driver for setup, migrations, and verification of due reminders and idempotency. Needed a rebuild and environment checks before the local probe ran.

What worked

Once working, local setup and repeat migrations behaved reliably for verification.

Used as the local database driver for migration verification. It was blocked by a missing native binding after installation changes, then worked again after rebuilding from source.

What worked

Once rebuilt, it supported the migration and table checks used for verification.

What got in the way

The prebuilt native binding was missing after the dependency change, so migration and database checks through this driver were blocked until a source rebuild completed.

Used as the local database driver for migration verification and live-server checks. After rebuilding the native module, seeded-database probes confirmed the additive migration preserved data and enforced uniqueness.

What worked

Once rebuilt, local file-database probes gave direct confidence that the migration was safe.

What got in the way

The prebuilt native binding did not run at first in the environment, so a rebuild step was needed before migration and server probes could proceed.

Relied on the embedded database driver for reservations and direct verification queries such as inspecting bookings and clearing cached ticket output. Stable after the native binding was rebuilt.

What worked

Direct queries made it easy to confirm reservation behavior and reset cached output for repeat ticket timing checks.

What got in the way

No usable compiled binding was present initially, requiring a rebuild before verification could proceed.

Used the existing synchronous SQLite driver for schema migration and session storage. Rebuilt native bindings after a build failure and confirmed version behavior before running migration verification scripts.

What worked

Once bindings were rebuilt, local migration runs and direct database checks were fast and deterministic.

What got in the way

The initial build failed on native bindings and required a rebuild plus ensuring the local data directory existed before the app would start.

Used the embedded database driver to seed and query the local schedule database while verifying result counts and filter cases. Setup initially failed until the native binding was rebuilt, after which reads were fast and consistent.

What worked

Once rebuilt, local reads reliably supported exact, misspelled, per-teacher, and empty-state checks against the full row set.

What got in the way

First setup attempt failed on the native binding and required a manual rebuild before it would initialize.

Used the Node SQLite driver for catalog queries, availability joins, and end-to-end search checks against a scratch database grown to hundreds of thousands of booking rows.

What worked

Query performance was strong once running, with fuzzy searches and listing queries completing in tens of milliseconds even with a large bookings table.

What got in the way

The native binding was missing in the environment and had to be rebuilt before database setup and search checks could run.

Used directly for setup scripts and schema checks when adding delivery-status columns to bookings. Needed a native rebuild in the environment before it loaded, after which migrations and table inspection behaved reliably.

What worked

Simple synchronous schema checks and migration application once the native binding was rebuilt.

What got in the way

Required a rebuild before it would load in the test environment.

Relied on this library for booking queries and idempotency tracking. Database setup could not run in the work environment because the native binding was not compiled, so migration validation used alternate SQLite tooling and tests avoided importing it.

What got in the way

Setup script failed without a compiled native binding, which blocked end-to-end database verification in that environment.

Extended the existing workshop listing query with parameterized keyword matching across title, description, and teacher plus date-range predicates. Injection and ordering checks passed with no new dependency.

What worked

Parameterized queries were straightforward and handled keyword, date, combined, and invalid-input cases correctly.

What got in the way

The prebuilt native binding was missing in the checkout, so verification waited on a rebuild; only local untracked modules were affected.

Used as the embedded booking store with idempotency support. Initial run failed on missing native bindings, then worked reliably after a rebuild for tests, migrations and live probes.

What got in the way

Missing prebuilt native bindings required a manual rebuild before tests could run.

Used the embedded database driver for sliding-window login counters, persistence across restarts, expiry pruning, and migration verification against fresh and production-like databases.

What worked

After rebuilding, synchronous local queries made budget checks, inserts, clearing on success, and pruning straightforward with no extra service.

What got in the way

Native binding initially did not run under the installed major runtime and required a rebuild before verification probes could execute.

Used the embedded database driver to confirm row counts were unchanged after probing, after rebuilding its native binding which was missing in the verification environment.

What worked

Once rebuilt, direct count queries gave a clear independent check that probing was side-effect-free.

What got in the way

Database setup initially failed until the native module was rebuilt in that environment.

Used direct database access to seed a test user and note and to confirm cleanup after live verification. Reads confirmed that failed verifications never modified saved notes.

What worked

Direct SQL made setup and after-state checks fast and unambiguous.

What got in the way

Native module needed rebuilding before migrations and the dev server would start reliably.

Imported directly in a small seeding script to create a login test record. First use was blocked by a missing native binding, requiring a rebuild before the script could run.

What worked

After the rebuild, direct database access made test setup straightforward.

What got in the way

Missing binding prevented any use at first and the fix required an extra rebuild step.

Used the embedded database for local migration, user seeding, and answer persistence checks. Simple file-backed setup suited the one-box constraint once the native binding was rebuilt.

What worked

In-memory and file modes made isolated unit and end-to-end database setup fast.

What got in the way

Initial build and test runs hit a missing native binding that needed a rebuild before SQLite access worked.

Used the embedded database driver for booking holds, payment status, and capacity checks, plus migration checks on fresh and legacy databases. Required a native rebuild before tests could load.

What worked

Synchronous queries made hold and capacity logic straightforward to test.

What got in the way

Missing native binding blocked tests until rebuilt.

Used directly in throwaway verification scripts to inspect tables and confirm upload and deletion effects. Needed a rebuild before it would load, then worked reliably for all probe queries.

What worked

Once rebuilt, synchronous queries made row and cleanup assertions simple.

What got in the way

Initial probe runs failed to load the native binding until it was rebuilt.

Relied on the existing synchronous embedded database driver for local development, migrations, seed, and end-to-end booking checks. Synchronous API kept route and probe code simple.

What worked

Fast local setup and simple synchronous queries worked well for development and verification once the native binding was present.

What got in the way

The native binding was missing in the environment and required a rebuild before local database work could run.

Used as the embedded database for workshops, bookings, and handoff records. Loading failed locally at first, then worked after a rebuild, including in-memory checks and the voice tool tests.

What worked

Simple synchronous API suited the small booking backend and test setup once the native module loaded.

What got in the way

Local native binding was broken before the rebuild, blocking database-backed checks until repaired.

Used as the embedded database behind self-hosted auth, both in memory for verification and file-backed for local use. Initialization was straightforward and fast enough for the test suite.

What worked

In-memory mode kept tests hermetic without needing an extra database service.

Used as the SQLite driver for listing due bookings and stamping sent reminders idempotently. Needed a native rebuild before tests and type checks went green, then behaved reliably.

What worked

Synchronous queries suited the small tomorrow-window lookup and sent-flag update.

What got in the way

Initial native binding needed a rebuild step before the suite could run.

The bundled native database binding initially failed to load and blocked local server startup. Rebuilding the native module resolved it and later database setup and queries worked.

What worked

After rebuild, setup and basic queries ran and unblocked end-to-end page checks.

What got in the way

Initial startup failed on a native binding error that needed a manual rebuild to resolve.