How to corrupt an SQLite database file

Post by mjmas » Tue, Jun 30, 2026, 11:22 AM UTC

toxik wrote: post #20

> One example of this occurred circa 2013-08-30 on the canonical repository for the Fossil DVCS. In that event, file descriptor 2 (standard error) was being erroneously closed (by stunnel, we suspect) prior to sqlite3_open_v2() so that the file descriptor used for the repository database file was 2. Later, an application bug caused an assert() statement to emit an error message by invoking write(2,...). But since fil…

Post by wat10000 » Tue, Jun 30, 2026, 12:29 PM UTC

cyberax wrote: post #10

zeroimpl wrote: post #9

Earlier quoted context omitted.

So is the official pronunciation of SQLite spelling out the letters then? I’d expect “a” not “an”…

I have never heard it pronounced in any other way than "s-q-lite".

Post by earth_tattoo » Tue, Jun 30, 2026, 1:18 PM UTC

seethishat wrote: post #22

To make the corruption more efficient, store the file on a RAID.

Post by rnio » Tue, Jun 30, 2026, 1:25 PM UTC

felix-the-cat wrote: post #26

I just finished building an open-source project using SQLite, and this makes me a little nervous. Is SQLite generally considered a reliable system? I've only had one experience with the DB becoming corrupted and that was because I used the Task Manager to force kill the process while it was running under a heavy load, and I felt that was understandable.

Post by Spooky23 » Tue, Jun 30, 2026, 1:28 PM UTC

earth_tattoo wrote: post #25

seethishat wrote: post #22

To make the corruption more efficient, store the file on a RAID.

Why do people shit on raid? I have been running RAID servers for over a decade with no issues, including a personal server with 5x16tb drives.