Rails validation defines valid states for each of your Active Record model classes. They are used to ensure that only valid details are entered into your database. Rails make it easy to add validations to your model classes and allows you to create your own validation methods as well. Using built-in validation DSL, you can do several kinds of validations.
When an Active Record model class fails a validation, it is considered an error. Each Active Record model class maintains a collection of errors, which display appropriate error information to the users when validation error occurs.
Rails built-in Validation Methods
||This validation is done by the user to accept a terms of service agreement by checking in a check box
||Validates whether associated objects are all valid themselves. Work with any kind of association.
||It validates whether a user has entered matching information like password or email in second entry field.
||Validates each attribute against a block.
||Validates that an attribute is not in a particular enumerable object.
||Validates value of an attribute using a regular expression to insure it is of correct format.
||Validates whether value of an attribute is available in a particular enumerable object.
||Validates that length of an attribute matches length restrictions specified.
||Validates whether an attribute is numeric.
||Validates that attribute is not blank.
||This is an alias for validates_length_of
||Validates that an attribute is unique in the database.
The following Rails methods skip validations and save the object to the database regardless of its validity. They should be used with caution.
valid? and invalid?
Before saving an Active Record object, a validation is done by Rails. If any error is produced, object is not saved.
The valid? triggers your validations, returns true if no errors are found and false otherwise.
The invalid? is simply the reverse of valid?. It triggers your validations, returns true if invalid and false otherwise.