5 Commits

Author	SHA1	Message	Date
Karl Seguin	e7be3c8b14	still trying to get this test to pass	2026-04-20 18:57:45 +08:00
Karl Seguin	55d7bae943	more busy timeout tricks	2026-04-20 18:42:55 +08:00
Karl Seguin	fcd3d1cd14	Use unsafe journal_mode during Pool test ... Can't use WAL, as it thread sanitizer reports false positives. The default, delete, causes busy timeouts. Let's try the unsafe memory!	2026-04-20 18:14:29 +08:00
Karl Seguin	b226a9ed52	Disable WAL mode for Sqlite pool test ... It seems like there are known false positives with thread sanitizer and sqlite. (There are various references to this in sqlite's wal.c and also possibly related https://bugzilla.mozilla.org/show_bug.cgi?id=1153409	2026-04-20 17:16:42 +08:00
Karl Seguin	6d0003ad2b	Sqlite ... This adds an app.storage which is a union around configurable storage engine (currently, only sqlite). It is _not_ being used anywhere right now. The goal is to get feedback on the implementation and then move cache to it. This doesn't expose a generic query API. The goal is that the storage will expose high level methods, e.g. `cacheGet(req: CacheGetRequest)` and every storage engine will translate the `storage.CacheGetRequest` as needed. A thin wrapper around the Sqlite C api is included, e.g. exec(SQL, .{args}) a `rows` and `row` fetcher. A connection pool is included. By default, an in-memory DB is currently created. And a `migrations` table with an id of `1` is created/inserted. I don't imagine needing fancy migratations.	2026-04-20 17:13:06 +08:00