Hello Cecil, I have multiple 30-40 GB Sqlite DB's which contain images as blobs. I back them up by copying them to my backup drive. Unless your application runs 24x7, I see no reason to do anything complicated with the backup.
My image blobs are in a table which contains an image and a rowid to ID the image. The meta data is all in a different table. It would be simply to split this out into multiple DB's but from a performance perspective, I don't see the point. It's plenty fast enough for my usage. I'm not using the Blob IO routines. I just copy them into memory in one go when I need them. If my machine was slower I might do it differently. As long as I can retrieve and view the images as fast as I can page them, I'm satisfied. I do have export routines to export them as images or CBR/CBZ files. I like them all in one file too. C Thursday, April 14, 2016, 4:18:58 PM, you wrote: CW> 2016-04-14 22:07 GMT+02:00 Clemens Ladisch <clemens at ladisch.de>: >> Cecil Westerhof wrote: >> > what is the best way to make a backup? >> >> With the backup API: <http://www.sqlite.org/backup.html>. >> (Also available as .backup in the shell.) >> CW> ?I should be more precise in my communication. :'-( CW> I prefer to make my backup with .dump. Then I have just a text based CW> backup. This works fine for the regular data, but not for photos: they can CW> be 13 MB big. (And I am not even using raw. When I am going to do that, CW> they will become much bigger.) So I would like to have my photos split out CW> when making the dump. CW> But maybe it will be better to use external blobs. CW> Something to think about. -- Teg mailto:Teg at djii.com
