<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SQLite on AltSql.com</title>
    <link>https://altsql.com/tags/sqlite/</link>
    <description>Recent content in SQLite on AltSql.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://altsql.com/tags/sqlite/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SQLite File Copied During a Write Passes AltSql Restore and Fails the SQLite Integrity Check</title>
      <link>https://altsql.com/sqlite-file-copied-during-a-write-passes-altsql-restore-and-fails-the-sqlite-integrity-check/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://altsql.com/sqlite-file-copied-during-a-write-passes-altsql-restore-and-fails-the-sqlite-integrity-check/</guid>
      <description>&lt;p&gt;Most case studies show a tool doing its job. This one shows AltSql Restore 0.5.0 passing a backup it should have failed, because that&amp;rsquo;s what the recorded run says, and because the way the backup was made is common enough to matter.&lt;/p&gt;&#xA;&lt;p&gt;The database is Chinook, the public sample database of a digital music store, as its project ships it for SQLite: one file of 1,007,616 bytes with 11 tables and 12 indexes. In this test an application keeps it as &lt;code&gt;app/chinook.db&lt;/code&gt; in SQLite&amp;rsquo;s default journal mode, and the nightly backup is a plain &lt;code&gt;cp&lt;/code&gt; of that file. Every night ended with &lt;code&gt;altsql-restore&lt;/code&gt; checking the copy, and with SQLite&amp;rsquo;s own &lt;code&gt;PRAGMA integrity_check&lt;/code&gt; run on the same copy for comparison. The three nights ran one after another on 31 October 2026.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
