by jonha4711 (Posted Sat May 14, 2016 10:51 am)
Is the following scenario viable?
This is written under the assumption that categories are part of the binary BLOB called 'Meta' in XnView.db's Images table. My photos, once in the database, tend to stay as they are as I work on copies.
1. After setting categories for my images, I access the database (with XnViewMP not running of course) via a self-written script that reads and writes all image filenames (or IDs) and the complete 'Meta' blobs to a separate file.
2. Later I have to recreate the database for whatever reason, but we can assume, for the sake of the discussion, that the image files themselves are completely unchanged and that there are no additions or deletions.
3. If then I read the 'Meta' blobs and filenames from my saved file and and write the blobs back into the newly created database, should that process recreate my categories as well?
I know this is probably a highly unsafe procedure and I will (try to) make sure that my database never gets corrupted and that I do have backups... but better safe than sorry.
Read Main Topic
Is the following scenario viable?
This is written under the assumption that categories are part of the binary BLOB called 'Meta' in XnView.db's Images table. My photos, once in the database, tend to stay as they are as I work on copies.
1. After setting categories for my images, I access the database (with XnViewMP not running of course) via a self-written script that reads and writes all image filenames (or IDs) and the complete 'Meta' blobs to a separate file.
2. Later I have to recreate the database for whatever reason, but we can assume, for the sake of the discussion, that the image files themselves are completely unchanged and that there are no additions or deletions.
3. If then I read the 'Meta' blobs and filenames from my saved file and and write the blobs back into the newly created database, should that process recreate my categories as well?
I know this is probably a highly unsafe procedure and I will (try to) make sure that my database never gets corrupted and that I do have backups... but better safe than sorry.
Read Main Topic