Schema Validation in MongoDB

MongoDB schema validation helps keep your data organized and correct. With MongoDB validation rules, we can set up guidelines for what data can be stored in our database. This makes it easier to ensure that all the information we save is reliable and useful.

In this article, We will learn about the Schema Validation in MongoDB, When to use Schema Validation and When MongoDB Checks Validation in detail by understanding various aspects

Mongodb Schema Validation

• Schema validation in MongoDB is a feature that allows us to set the structure for the data in the document of a collection.
  
• We follow some set of rules and validation rules which ensure that the data we insert or update follows a specific predefined schema and ensures the data must have only specific datatypes, required fields and validation expressions mentioned in the predefined schema.
  
• When we create a collection for the first time and we want it to meet specific criteria then we can define the collection with the schema validation rules.
  
• These validation rules can include specifying the required fields we want and the datatype for those fields and also allow the users custom expressions. We use the command $jsonSchema for specifying the rules.

When to use Schema Validation

• Schema validation sets rules for how documents should look in our database. When developing a new application, we might not want to use schema validation since the incoming data could change and we're still figuring out the structure.
  
• However, once we have a clear understanding of our application and know the types of data each field should hold, we can use schema validation. For example, if we have a collection to store employee usernames then we can set validation rules to ensure that usernames are always stored as strings. This prevents users from accidentally entering other data types.
  
• For instance, we have a collection 'students' and you want to have fields like name, id, age and department for our collection to store in it.

Step 1: We create a collection named of 'students' using the createCollection() command.

Step 2: With the '$jsonShema' command inside the validator we specify the schema validation rules. Here with the required property we give a list of fields that every document must have when inserted into the collection.

Step 3: Give all the fields and their datatypes inside the properties.

// Example schema validation for a collection named 'Students'
db.createCollection("Students", {
 validator: {
 $jsonSchema: {
 bsonType: "object",
 required: ["name", "id", "age", "department"],
 properties: {
 name: {
 bsonType: "string",
 description: "Name must be a string."
 },
 id: {
 bsonType: "int",
 description: "id must be an integer."
 },
 age: {
 bsonType: "int",
 minimum: 10,
 description: "Age must be an integer greater than or equal to 10."
 },
 dept: {
 bsonType: "string",
 description: "Department must be a string."
 }
 }
 }
 }
});

Step 4: Now try to insert the documents one by one into the collection with insertOne() command.

Query:

When we insert data according to validation rules it means Valid Document.

//inserting a record into Students
db.Students.insertOne({
 name: "el",
 id: 2001,
 age: 11,
 department: "IS",
});

Output:

When we will try to add Invalid Documents to our collection.

Query:

//inserting a record into Students
db.Students.insertOne({
 name: "will",
 id: 2002,
 age: 14,
});

Output:

Explanation: Here, you can see the first document consists of all the required fields in the collection so it is inserted successfully. Whereas, the second document is missing the department field, in this case it is considered an invalid document and throws an error as it doesn't meet the criteria specified in the schema validation. Hence MongoDB rejects the document to be inserted into the collection.

When MongoDB Checks Validation

We should know that whenever we create a new collection with schema validation, MongoDB checks for validations only during updates and inserts in that collection. When we specify validation rules for a pre-existing, non-empty collection only the documents that are inserted after are checked for validations.

The documents already present in the collection are not checked for validation until they are altered. When we want to update the already existing schema we use 'collMod' command.

db.runCommand({
 collMod: "Students",
 validator: {
 $jsonSchema: {
 bsonType: "object",
 required: ["name", "id", "age", "department", "marks"],
 properties: {
 name: {
 bsonType: "string",
 description: "Name must be a string.",
 },
 id: {
 bsonType: "int",
 description: "ID must be an integer.",
 },
 age: {
 bsonType: "int",
 minimum: 10,
 description: "Age must be an integers greater than or equal to 10.",
 },
 department: {
 bsonType: "string",
 description: "Department must be a string.",
 },
 marks: {
 bsonType: "int",
 minimum: 0
 description: "Marks must be integer greater than or equal to 0.",
 },
 },
 },
 },
});

Explanation: Here we included the marks field in the required property. We used 'collMod' to modify the schema defined earlier.

Note: 'collMod' will fail if the collection has the already existing documents that don't follow the validation rules. So to modify the schema with 'collMod', ensure that the documents already present in the collection must be updated according to the schema or removed.

What Happens When a Document Fails Validation

When a document fails schema validation in MongoDB:

• MongoDB rejects the document insertion or update.
  
• It returns an error specifying which validation rules the document violated.
  
• No changes are applied to maintain data integrity.
  
• Developers handle validation errors in application code.
  
• Schema updates may require modifying existing documents to match new rules.

Conclusion

In conclusion, using MongoDB schema validation is important for keeping your data accurate. By applying MongoDB validation rules, you can avoid mistakes and make your database stronger. Good MongoDB data validation leads to better data quality and smoother application performance.