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
If a publisher alters the structure of a source (add, rename, duplicate, remove column) while another is modifying the metadata of the same source, the structural changes will not be propagated in the metadata stored in mx_sources. This is because the version loaded into the metadata editor predates the structural edits and once saved, they will overwrite the version of the metadata containing the structural changes saved from the table editor.
An approach to avoid this could be to do a check on date_modified to ensure that the source has not been updated in the meantime.
The text was updated successfully, but these errors were encountered:
This issue should probably be resolved once the metadata editor is integrated with the Node.js: editing metadata for a given source will be locked until table editing is completed, and vice versa.
If a publisher alters the structure of a source (add, rename, duplicate, remove column) while another is modifying the metadata of the same source, the structural changes will not be propagated in the metadata stored in
mx_sources
. This is because the version loaded into the metadata editor predates the structural edits and once saved, they will overwrite the version of the metadata containing the structural changes saved from the table editor.An approach to avoid this could be to do a check on
date_modified
to ensure that the source has not been updated in the meantime.The text was updated successfully, but these errors were encountered: