The default defined SQLite connection leaves journal_mode, busy_timeout, and synchronous set to null, so concurrent API requests (e.g. hitting /api/schedules and /api/incidents in quick succession) intermittently fail with "database is locked". Enabling WAL mode and a busy timeout by default would possibly prevent this.
The default defined SQLite connection leaves
journal_mode,busy_timeout, andsynchronousset to null, so concurrent API requests (e.g. hitting /api/schedules and /api/incidents in quick succession) intermittently fail with "database is locked". Enabling WAL mode and a busy timeout by default would possibly prevent this.