2018-07-05, 09:17
1) locking can be quite challenging.
In fact, you need for everything an additional checkbox, if to lock or not.
This will make the GUI and settings quite unusable i guess, for a low benefit.
In fact, on scraping you have the checkboxes what to scrape.
If you untick "artwork", we would not scrape, thus not overwriting artworks...
Or do it the other way round - untick artwork in global settings, and only activate selective on scrape...
"Locking" is not what we want to implement...
2) well, we might even remove this.
The method does nothing beside deleting the database, and restarting TMM.
3) we already have DB backups in our /backups/ folder.
So technically you could fire up an old version, and recreate the NFO files (if the movie structure has not changed)
When we delete files, the default is to move them to a .deletedByTMM folder inside your datasource.
Spamming folders with .bak files is not what we want to archieve...
But yes, existing NFO files are not considered here.
We would always write (on changes) with our information in database (which we might have read from NFO file also)
We even keep unknown entries when writing NFO - so no information should get lost
Have no idea what we could do to further improve the data protection.
In fact, you need for everything an additional checkbox, if to lock or not.
This will make the GUI and settings quite unusable i guess, for a low benefit.
In fact, on scraping you have the checkboxes what to scrape.
If you untick "artwork", we would not scrape, thus not overwriting artworks...
Or do it the other way round - untick artwork in global settings, and only activate selective on scrape...
"Locking" is not what we want to implement...
2) well, we might even remove this.
The method does nothing beside deleting the database, and restarting TMM.
3) we already have DB backups in our /backups/ folder.
So technically you could fire up an old version, and recreate the NFO files (if the movie structure has not changed)
When we delete files, the default is to move them to a .deletedByTMM folder inside your datasource.
Spamming folders with .bak files is not what we want to archieve...
But yes, existing NFO files are not considered here.
We would always write (on changes) with our information in database (which we might have read from NFO file also)
We even keep unknown entries when writing NFO - so no information should get lost
Have no idea what we could do to further improve the data protection.
