1 comments

  • simonw1 hour ago
    <a href="https:&#x2F;&#x2F;github.com&#x2F;nsrht&#x2F;time-travel-sqlite-debugger&#x2F;blob&#x2F;main&#x2F;watcher.php" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;nsrht&#x2F;time-travel-sqlite-debugger&#x2F;blob&#x2F;ma...</a> works by checking the mtime on the database file (and -wal file) once per second and creating a backups&#x2F;unixtime_database.sqlite file if anything has changed, then keeps the last 50 copies.<p>So OK for smaller database files but not great if you&#x27;re pushing into a GB+ of data.<p>I&#x27;m not convinced by the way it copies the files - I think using a &quot;vacuum into&quot; backup would be safer then file copies.<p>Litestream offers point-in-time recovery for SQLite by backing up chunks of WAL directly, which I expect is a lot more efficient than this mechanism.
    • dcreater56 minutes ago
      And using php of ai languages to do this...?