Thread: Move Library : function and performance
View Single Post
Old 12-09-2015, 07:48 PM   #5
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,786
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by eschwartz View Post
The expected behavior is that each individual file that calibre knows about will be moved, not copied.

So if all the files are copied something is wrong (file locking?)
The time taken to do the so-called 'move' (27 secs) is the approximately the same as File Explorer takes to 'copy' the same folder (24 secs) - a File Explorer 'move' is of course instantaneous

If files are locked calibre will normally thrown an error.

The contents of the old and now library folders are not symlinked, hardlinked or otherwise exotically associated.

I'll have to look up out how to get the file Object-Ids (fsutil I think) - if they're being copied they will be different, if they're being moved they'll be the same.

BR
BetterRed is offline   Reply With Quote