That is a good point, though I was hoping that implementation details like the database library can be handled internally, and admin tasks wrapped within the svn frontend.
-----Original Message----- From: Daniel Shahaf <d...@daniel.shahaf.name> Sent: 12 August 2019 14:41 To: Jens Christian Restemeier <j...@playtonicgames.com>; users@subversion.apache.org Subject: Re: sqlite[s11]: database disk image malformed Jens Restemeier wrote on Mon, 12 Aug 2019 11:19 +00:00: > Thanks to a power cut last week while updating I’ve got a few > corrupted > workspaces: > > Error: sqlite[S11]: database disk image is malformed > Error: Additional errors: > Error: sqlite[S11]: database disk image is malformed > > I'm currently trying to repair them from a fresh checkout, but I was > wondering: > - sqlite3 supposedly does journaling, shouldn't it be possible to > repair the database from the journal? Is there a "svn cleanup" option? > (The only thing online I found was to dump to sql and reimport into a > new database, which failed after quite some time...) Note that that error message is reported by SQLite; Subversion simply relays it. You might want to ask this question on the SQLite mailing list. Cheers, Daniel
