morten71 wrote:
How does the validator classes function when doing save, delete and update multi operations?
This is explained in detail in the docs. Basically, if you do something like:
adapter.SaveEntityCollection(myCollection);
then each entity inside the entity passes through yourValidator.ValidateEntityBeforeSave and yourValidator.ValidateEntityAfterSave. Similar with adapter.DeleteEntityCollection(myCollection) and yourValidator.ValidateEntityBeforeDelete.
Now, if you do something like:
adapter.ValidateEntityBeforeDelete(newValues, filter);
... it's different, as you are not working with entities, but with a set of new values and a filter. In that case you should write your validation in your own business logic. You should establish what you want to validate and how. In most cases you could do that just using the filter.