6
« on: 2014-03-05 15:21:56 »
> Have you tried Database | Jpeg Compress? (of course, keeping a backup of your current database). For now, that would seem like the best solution to me. It should greatly reduce the database size.
Thanks, but Jpeg Compress is useless. Compressing to 50% saves around 1 MB:
The database compact and repair process succeeded.
Old size: 2,147,483,648 bytes
New size: 2,146,553,856 bytes
Compressed by: 0.0 %
> Also, are you sure that simply starting a new database is no option? I see that you have a lot of keywords and if those were painstakenly entered by hand, I can see how you don't want to lose them. But if they were auto-generated maybe you can just start a new database (in SQLite 3 format if you wish).
Most of the keywords were auto generated but I don't want to lose my user-generated fields, keywords, galleries and searches. I did try starting to create a new database in SQLite 3 format but gave up because of the slow time to create thumbnails.
Regarding Thumbnail size regardless of whether it is a new database or I rebuild thumbnails any size over 120 is cropped. I've no idea how you can make good large thumbnails.