View Single Post
Old 12-09-2015, 11:40 PM   #11
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,806
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by kovidgoyal View Post
Works for me. All I get left behind is the original folder with metadata_db_prefs_backup.json in it. All the actual books get moved. I should probably fix metadata_db_prefs_backup.json
Yes I think it would be better to remove those files and the folder at the end of the move.

Should the deletes happen progressively as books are coped? I can set a task to monitor the filesystem operations on the library as its being moved.

The library folder that failed to delete anything would have had a disposition of Read Only (only the library folder not the contents) -- I wonder?

Aside : if some bright spark created shortcuts to their favourite books and then they moved their library, the shortcuts would be rendered irreparable; the repair service (Distributed Link Tracking) relies on the fact that files and folders will retain their Object Ids when they are renamed or moved within the same domain.

BR
BetterRed is online now   Reply With Quote