Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    Well, backups can be done via the SQLite Backup API. I'll acknowledge SQLite might not be quite as safe by default, since, unlike service-oriented systems, SQLite clients talk to the database file more directly. That said, SQLite does use a journal to protect against system failures, and should be reliable if the host OS properly supports the locking primitives SQLite uses (network disk I/O does not). The official site lists several scenarios which will lead to a corrupt SQLite database. Commented Dec 2, 2013 at 23:32
  • SQLite is transactional. Use the Backup API or adapt MediaWiki's backup script to perform online backups. Your general understanding of SQLite's security model is correct. The official security advice is 'use common sense': think about how people could access your database file and design your web application accordingly. Commented Dec 2, 2013 at 23:32
  • @Brian -- I'd be hard pressed to think of another DB that has an entire page dedicated to "how this database can be corrupted". I will add that I do find the sql lite project amazing -- they likely have that page because they are kind of nuts and also have something like 10 lines of test code for every line of production code and really like to be sure and thorough. Commented Dec 3, 2013 at 3:57