Data Propagation - no write back to propagate categories

[hluxem]

I propose to eliminate the initial meta data write back if no meta data is propagated. No write back is required when only categories or attributes are propagated.   

Background:
This is in response to the following bug report.

https://www.photools.com/community/index.php?topic=11624.msg83232#msg83232

I do like to promote categories only to version. Besides being fairly slow as reported in the thread, my masters are read only and I get the warning triangle. There is no need to write back changes when only categories or attributes are propagated.

So you force a propagation via F4,P. The propagation is not caused by you changing the categories of the master.

I think that's what you have to do initially to get the categories synchronized. It's really fast afterwards when you just change categories.

[akirot]

++++++++++ 1

Please switch back to the requested behaviour - it has been in place up to and including IMatch 2020.

[Mario]

++++++++++ 1

Please switch back to the requested behaviour - it has been in place up to and including IMatch 2020.

I don't understand. Nothing with how propagation works has changed for a long time. I see no changes in forced propagation in the version control system in IMatch 2020 or 2021.
What do you mean exactly? There is nothing to switch back to.
Do you recall what and when it happened?

What we discuss here is a new set of new optimizations which checks if there is anything in the rules of the master being propagated which causes metadata propagation (rating, label, annotations, @Keyword categories, rule sets, ...) and of not, skip write-back. This is a sensible optimization for users who only propagate categories or Attributes and I will look into this for one of the next releases.

[Mario]

I have added an optimization that checks each relation rule for each master being propagated during a forced propagation to see if anything related to metadata is propagated (rating, label, tag groups, annotations).
If this is not the case, no write-back is performed anymore.

This should be a welcome improvement for users only propagating categories or other in-database objects like collections or Attributes.

[hluxem]

Great!

Thank you so much! It's indeed a nice improvement!

Heiner