deblan-mirror/abraunegg-onedrive
deblan-mirror/abraunegg-onedrive
1
0
Fork 0
mirror of https://github.com/abraunegg/onedrive synced 2026-03-14 14:35:46 +01:00
Code Issues Projects Releases Wiki Activity

Fix Bug #3501: If using 'sync_list' only add new JSON items early (#3505)

Browse source 
* When using 'sync_list' and renaming online entries, only update the local database if the provided JSON is not in the database already to allow applyPotentiallyChangedItem() to operate as expected
This commit is contained in:
abraunegg 2025-10-31 09:32:37 +11:00 • committed by GitHub
commit bd94f821b7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 12 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

14
src/sync.d
View file

@ -6129,8 +6129,18 @@ class SyncEngine {
// So that this path is in the DB, we need to add onedriveJSONItem to the DB so that this record can be used to build paths if required
if (parentInDatabase) {
// Save this JSON now
saveItem(onedriveJSONItem);
// Parent is in DB .. is this a 'new' object or an 'existing' object?
// Issue #3501 - If an online name name is done, the item needs to be 'renamed' via applyPotentiallyChangedItem() later
// Only save to the database at this point, if this JSON 'id' is not already in the database to allow applyPotentiallyChangedItem() to operate as expected
Item tempDBItem;
itemDB.selectById(onedriveJSONItem["parentReference"]["driveId"].str, onedriveJSONItem["id"].str, tempDBItem);
// Was a valid DB response returned
if (tempDBItem.driveId.empty) {
// No .. so this is a new item
// Save this JSON now
saveItem(onedriveJSONItem);
}
}
}
}