Dan Stillman bdaecbb5cc Detect database corruption reported by a transaction's commit ... We only ever checked for corruption errors from transactions in queryAsync(), so a corruption error raised by the COMMIT that mozStorage runs itself bypassed the check. A 10.0 schema upgrade -- which heavily exercises the database -- that failed due to corruption showed "Database upgrade error" and a single Sqlite.sys.mjs frame instead of the prompt offering to restore from a backup. Two users reported this, but it's not clear what triggered it -- corruption usually occurs during a statement, which we did catch. There may have been some statement transaction whose corruption error was caught and ignored rather than being left to abort the transaction, causing SQLite to then block the commit. That's what the test does, and it fails without the fix. https://forums.zotero.org/discussion/133611/		2026-09-08 16:01:23 -04:00
..
content	Detect database corruption reported by a transaction's commit	2026-09-08 16:01:23 -04:00
locale	Tell the user to set up syncing again if credentials can't be decrypted	2026-09-04 18:12:31 -04:00
skin/default/zotero	Center single-paragraph items pane status messages when they wrap	2026-09-02 22:16:13 -04:00