mirrors/zotero
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Mark fields as changed when migrating Extra fields

Browse source 
We're not migrating fields yet, but when we do, I think marking them as
changed will be the safer option. We'll just have to make sure that
conflicts without differences are resolved automatically on all
platforms.
This commit is contained in:
Dan Stillman 2019-09-28 06:16:19 -04:00
parent 54b268fe01
commit 8aeb6f7fe4
1 changed files with 0 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
chrome/content/zotero/xpcom/schema.js
View file

@ -622,13 +622,6 @@ Zotero.Schema = new function(){
for (let item of items) {
let changed = item.migrateExtraFields();
if (!changed) continue;
// Don't mark the item as changed if it's not already so that every client doesn't try
// to upload new data. While in theory the changes should be the same and automatically
// merged, it's risky and unnecessary, since server data will also be updated on schema
// changes. (It would also create a huge amount of write traffic.)
if (item.synced) {
item.synced = true;
}
await item.saveTx({
skipDateModifiedUpdate: true,
skipSelect: true