Usually instances of models (objects) are created using a
ModelForm. You know the drill: The user inputs some values in the form, hits submit and sends a
POST request with the data. In the view function, we do a model validation using
form.is_valid() and then save the object in the database. This gives a basic level of validation for the model fields.
But what if we want to do a more comprehensive validation on the object? And what about a scenario where we want to create objects in some other way than using forms? Let’s say through an API call. How do we validate the objects in that case?
That is what validators are for. Validators are callable functions that will check the object fields and raise
ValidationError if they contain values that don’t meet our desired criteria. In case of
ModelForm the validation is done when we call
form.is_valid(). Note that if we create an instance of the model ourselves, validators will not be run automatically. So we need to validate the objects first before saving them.
Let’s say we have a model called Person. Each person has a first name, a last name and an age. And for some reason, we don’t want to save the person in our database if their age is less than 18. We can create a validator that checks for that.
Now just before we save the object, we ask django to validate it by calling the
person.full_clean() will run the relevant validators for all fields of the
person object. In this case it will run the
validate_age function on the
person.age field and throws an exception. This prevents this object from being saved. So young John will not be saved into the database!