The behavior of Google Drive for a file copy operation with overwrite is not standard or expected behavior for most file systems (e.g. (Checked by comparing the modified file time on "G:\My Drive" to the same file in the web browser). The modified time is the current time instead of the source file's modified time.ī) The file's local cached metadata in Google Drive for Desktop does not reflect the same modified time as the cloud storage. There are now two problems:Ī) The copied file has the wrong modified time in the the cloud (checked using Google Drive via web browser). (The file's modified time is correct, both in the cloud and the local cached modified time.)Ģ) Copy the same local file to the "G:\My Drive" folder and overwrite the original. The modified time matches the original source local file. Expected behavior: When copying a file and overwriting an existing file, the modified time of the source file should be preserved.Įxample using Google Drive for Desktop (Windows):ġ) Copy a new file to the "G:\My Drive\" folder. the modified time in the cloud matches the modified time of the local file.)Ģ) Upload the same file to Google Drive via web browser, overwriting the existing file, and it now has the wrong modified time. The file modified date is an important piece of information about the file and should not be lost by a file copy operation.Įxample using Google Drive with web browser file upload:ġ) Upload a new file to Google Drive via web browser. Google Drive does not preserve file modified date when copying and overwriting an existing file.
0 kommentar(er)
