I just got done syncing my Dropbox with odrive and found that all of my files were not only touched affecting the “date added” value, but the “Date Modified” value was updated as well even though the files were not changed at all.
While I understand that directories are going to be created new and have new dates, it is most disconcerting that file metadata is tainted by odrive in that it doesn’t preserve the last modified dates for files that are synced.
Then again, Dropbox was not doing much better by being unable to support the preservation of file metadata until late 2016- 10 years after they launched.
Honestly, it seems like every single cloud storage provider has some fatal flaw that makes it unusable to anyone except amateur users who don’t understand the implications of a cloud provider that doesn’t preserve file metadata, which sadly is most of them. Will files written to an “encrypted drive” have their metadata preserved or are they also at the mercy of the the antiquated API you use for the provider?
Setting this additional field is a secondary action in the upload process and is not considered a “requirement” for successful upload, so it is possible for that action to fail and the file to be uploaded to Amazon anyway.
In this case the file will not have the custom parameter and the modtime will be seen as the upload time when you download the file again.
More specifics: the files that had their “last modified” date changed were in a directory that got renamed.
This should definitely NOT affect “last modified” date of the file.
The problem is that in Bridge CS5, the "Date File Modified" entry does not update if I update a Canon CR2 RAW file that had previously been edited. The reply seems to indicate that Brian believe the problem is with CS3, but the problem lies with CS5.
The same applies for DNG files and possibly other file types, but I have not checked that yet. The CS3 suite works as expected and I was just comparing the unexpected results of CS5 with CS3 as a sanity check. I am wondering if this is a CS5 issue rather than being a Bridge issue since I believe that Bridge only displays the file information, but does not create it.
What appears to be the happening is whenever a file is considered “moved” (which may not mean that the file actually moved), but some conditions might indicate otherwise, the file modification date is updated as if to indicate there was a file change when in fact there wasn’t.
This defeats the purpose of syncing as syncing relies on the modification dates to be accurate in order for it to work. If someone has an explanation as to what conditions cause the modification date to be updated on a sync that would be helpful.
Renaming a folder should not affect the modtime of the files inside. Even if the files were re-uploaded, for some reason, odrive will still try to send the modtime as seen on the filesystem, if possible.