You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the compare noupdate xml script detects the value of forcecreate (1), and we can have a mode that allows to update data on existing items only (2), I'm thinking that these best be combined and that the load_data method should always pick apart each item and, if the item has the forcecreate='0' attribute, it is only actually loaded if the item already exists in the database.
Now that the compare noupdate xml script detects the value of forcecreate (1), and we can have a mode that allows to update data on existing items only (2), I'm thinking that these best be combined and that the load_data method should always pick apart each item and, if the item has the forcecreate='0' attribute, it is only actually loaded if the item already exists in the database.
What do you think @pedrobaeza, @hbrunn?
And do we need to keep the init_no_create mode in that case?
(1) OCA/OpenUpgrade#1060
(2) #80
The text was updated successfully, but these errors were encountered: