optimise a move via GUI and any re-hashing, due to FS move, or Transform, etc. to update the last_hash_dt so we dont keep redoing the md5 hash as ctime > last_hash_dt, but there is no new content so no new last_hash_dt was being modified
This commit is contained in:
3
TODO
3
TODO
@@ -8,9 +8,6 @@
|
||||
FIX: BUG-69
|
||||
TEST: what if we try to move a path in settings, should not allow this?
|
||||
|
||||
* when we do a legitimate move of a file, update last_scanned_dt otherwise FS change is newer, and it will 're-scan'
|
||||
* when we scan and there is no hash diff then, update last_scanned_dt otherwise FS change is newer, and it will 're-scan' continually
|
||||
|
||||
* remember last import dir, so you can just go straight back to it
|
||||
|
||||
* in Fullscreen mode and next/prev dropped out of FS when calling /viewlist route
|
||||
|
||||
Reference in New Issue
Block a user