Handling of large collections and errors

[Fionn B.]

To find out what happens I started a test with picapport on our complete family archive with more than 25.000 pictures.

Looks like "@all" stops working if you have more than 10.000 pictures available, because the sql engine throws an exception about too big result sets. Unfortunately in the frontend, this looks just like picapport crashed, no clue why.

Also, the cache filled up the data partition quickly and the directory crawler ran out of disk space. Unfortunately it looks like picapport does not gracefully recover from that, even when more space is made available later. You start getting loads of java exceptions and tracebacks and slideshows mostly display "missing image" instead of the actual picture.

Running out of space is a rather common scenario. For such events I would wish to have a way to export / backup all the application-settings and configured users to some sort of XML dump or whatever, so that I can have the application rebuild the DB from scrantch without having to re-enter all the little tids and bits from scratch. Not to mention the upload tags, which get lost.