Problem/Motivation
@yched brought up the following point in #1266748: Changing cardinality lower than highest existing delta causes data loss upon save
just wanted to remind a comment made earlier, that this approach could allow a cardinality change on a dev site with fewer content, and then let it be deployed on prod, where it might have been rejected if done directly on the prod backend UI because the prod site has more content.
If the data loss that currently happens when cardinality gets lowered is considered critical, the patch here is more a partial safeguard than a fix. There can still be data loss, depending on the site instance on which the config change is attempted.
@berdir replied:
Yeah. I guess we could look into config sync validators if we think this is important enough. But I'd only consider that if those are capable of only doing the check if we can see that it changed, otherwise it would be a lot of queries all the time.
Seems like a good idea to look into, since we have a lot of these conditional validation errors based on content presence or not.
Comments
Comment #3
Wim Leers