one of the reasons why I don't want it to validate while retrieving or loading is for performance.
reason 2:
the data is from the database due to legacy (including current application earlier bug, or older data would have been processed using previous rules at that time.) & I want to perceive that the data is valid when loaded from the persisting mechanism.
I tried dependency mechanism,
where the validator is injected based on scope (business component) & the entity is retrieved within the scope. However, my validator requirement to use validator is determined based on the data content (that is period of the createdt column) retrieved in the entity.
so seems like I can't use dependency injection mechanism in this scenario.
If the validation can be turned off while retrieving.
then my validation code can look for the createdt & apply my validation only when the data is modified or when it is required based on conditions inside the validator methods.