When updating data attached to a collaboration server via sql, what is necessary to ensure changes are triggered?

Question

Is changing the version sufficient? (e.g. below). I understand this is risky.

UPDATE tbl_flows
SET
  FLOW_TYPE = 'PRODUCT_FLOW',
  VERSION = VERSION + 1
WHERE FLOW_TYPE = 'WASTE_FLOW'
  AND ID = 525;

Comments

Oh I see a similar question that is python based, so I think the answer is that yes the version is sufficient

https://ask.openlca.org/8835/comit-changes-existing-processes-flows-collaboration-server

---

In addition updating the last_change value to the current time would be good, to ensure a unique data set. If e.g. someone changes the data set in the same time on the server, the versions of both would be the same and openLCA would not recognize the changes.

In summary: version and last_change are used to identify if a data set has changed

Answer 1

openLCA recognized a change of a data set in the context of Collaboration Server, by comparing version and last_change value. If both are the same, data sets are identified as unchanged.

If you want a change to be recognized as such, one of the values needs to be updated. To have unique identification for conflicting changes, it is strongly recommended to increase the version, and also update the last_change value, to avoid conflicting changes of the same data set (e.g. both set the same version)