docbee-fschrader commented on issue #15276: URL: https://github.com/apache/grails-core/issues/15276#issuecomment-3661438718
My thoughts: 1. That would be my preference because it would restore the behavior from grails 6 and require no changes when upgrading to grails 7. As to your question, how to handle cascades: Should that maybe be decided by the domain mapping property `cascadeValidate`? 2. If I were to use the attribute, I would expect it to skip validation on all flushes. That option would require changes in the process of updating an app from grails 6 to grails 7. My question for that option would be, whether it's possible to set the attribute for a `withNewTransaction` closure? 3. I agree, that it's clear, but it can potentially require a lot of changes when updating an app from grails 6 to grails 7. There could be cases, where it isn't decidable when starting the transaction, whether validation for a domain should be skipped or not. A simple example of that would be a method that allows to update two properties and only skips validation, if one of the properties isn't updated (more complex instances of that scenario exist in the project I'm working on). Options 1. and 2. seem more flexible because the decision of validating or not is made when save is called. 4. As an end user I agree it would be inconvenient 😅 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
