Deleting documents in Express

Introduction

Deleting documents lets you remove unwanted or outdated data from your database. It keeps your app clean and up to date.

When a user wants to remove their account or data.

When cleaning up old or expired records automatically.

When an admin deletes inappropriate content.

When correcting mistakes by removing wrong entries.

When freeing up space by deleting unused documents.

Syntax

Express

Model.deleteOne(filter, callback)
Model.deleteMany(filter, callback)
Model.findByIdAndDelete(id, callback)

deleteOne removes the first document matching the filter.

deleteMany removes all documents matching the filter.

Examples

Deletes one user with the given email.

Express

User.deleteOne({ email: '[e-mail]' }, (err) => {
  if (err) console.error(err);
  else console.log('User deleted');
});

Deletes all posts that are not published.

Express

Post.deleteMany({ published: false }, (err) => {
  if (err) console.error(err);
  else console.log('All unpublished posts deleted');
});

Deletes a comment by its unique ID and logs the deleted document.

Express

Comment.findByIdAndDelete('64a1f2b3c4d5e6f7a8b9c0d1', (err, doc) => {
  if (err) console.error(err);
  else console.log('Deleted comment:', doc);
});

Sample Program

This Express app connects to MongoDB and defines a route to delete a user by their email. It uses deleteOne to remove the user document. If no user matches, it sends a 404 response. Otherwise, it confirms deletion.

Express

import express from 'express';
import mongoose from 'mongoose';

const app = express();
app.use(express.json());

const userSchema = new mongoose.Schema({
  name: String,
  email: String
});

const User = mongoose.model('User', userSchema);

// Connect to MongoDB
mongoose.connect('mongodb://localhost:27017/myapp');

// Route to delete a user by email
app.delete('/users', async (req, res) => {
  try {
    const result = await User.deleteOne({ email: req.body.email });
    if (result.deletedCount === 0) {
      return res.status(404).send('User not found');
    }
    res.send('User deleted successfully');
  } catch (error) {
    res.status(500).send('Error deleting user');
  }
});

app.listen(3000, () => {
  console.log('Server running on http://localhost:3000');
});

Important Notes

Always check if the document exists before or after deleting to handle errors gracefully.

Use deleteMany carefully to avoid removing too much data by mistake.

Deleting documents does not undo automatically; consider backups if needed.

Summary

Deleting documents removes unwanted data from your database.

Use deleteOne, deleteMany, or findByIdAndDelete depending on your need.

Handle errors and check results to keep your app stable.

Practice

1. What does the deleteOne() method do in Express when working with a database?

easy

A. Deletes a single document that matches the filter criteria.

B. Deletes all documents in the collection.

C. Updates a document instead of deleting it.

D. Finds a document but does not delete it.

Solution

1. Step 1: Understand deleteOne() purpose

   The deleteOne() method removes only one document that matches the given filter.

2. Step 2: Compare with other methods

   deleteMany() deletes multiple documents, and find() only retrieves data without deleting.

3. Final Answer:

   Deletes a single document that matches the filter criteria. -> Option A

4. Quick Check:

   deleteOne() = deletes one document [OK]

Hint: Remember: deleteOne removes just one matching document [OK]

Common Mistakes:

• Confusing deleteOne with deleteMany
• Thinking deleteOne updates documents
• Assuming deleteOne finds but does not delete

2. Which of the following is the correct syntax to delete a document by its ID using Mongoose in Express?

easy

A. Model.findByIdAndDelete(id, callback);

B. Model.deleteById(id);

C. Model.removeById(id);

D. Model.deleteOneById(id);

Solution

1. Step 1: Recall Mongoose method for deleting by ID

   The correct method is findByIdAndDelete() which deletes a document by its ID.

2. Step 2: Check syntax correctness

   Only Model.findByIdAndDelete(id, callback); matches the official Mongoose syntax.

3. Final Answer:

   Model.findByIdAndDelete(id, callback); -> Option A

4. Quick Check:

   Use findByIdAndDelete to delete by ID [OK]

Hint: Use findByIdAndDelete to remove by ID [OK]

Common Mistakes:

• Using non-existent methods like deleteById
• Confusing deleteOne with findByIdAndDelete
• Missing callback or async handling

3. What will be the output of this code snippet in Express using Mongoose?

Model.deleteMany({ status: 'inactive' })
  .then(result => console.log(result.deletedCount))
  .catch(err => console.error(err));

medium

A. An error because deleteMany does not return deletedCount.

B. The entire deleted documents array.

C. Number of documents deleted with status 'inactive'.

D. Undefined because deleteMany returns nothing.

Solution

1. Step 1: Understand deleteMany return value

   deleteMany() returns an object with deletedCount indicating how many documents were deleted.

2. Step 2: Analyze the console.log statement

   The code logs result.deletedCount, so it outputs the number of deleted documents matching the filter.

3. Final Answer:

   Number of documents deleted with status 'inactive'. -> Option C

4. Quick Check:

   deleteMany() returns deletedCount [OK]

Hint: deleteMany returns deletedCount in result object [OK]

Common Mistakes:

• Expecting deleted documents array
• Assuming deleteMany returns nothing
• Confusing deletedCount with total documents

4. Identify the error in this Express Mongoose code snippet for deleting a document:

Model.deleteOne({ _id: id }, (err, doc) => {
  if (err) console.log(err);
  else console.log(doc);
});

medium

A. The filter object is missing required fields.

B. The deleteOne method does not accept a callback.

C. The method should be deleteMany to delete one document.

D. The callback parameter doc should be result to access deletion info.

Solution

1. Step 1: Check callback parameters for deleteOne

   The second callback parameter is a result object, not the deleted document itself.

2. Step 2: Understand what doc represents

   It should be named result or similar to reflect it contains deletion info like deletedCount, not the document.

3. Final Answer:

   The callback parameter doc should be result to access deletion info. -> Option D

4. Quick Check:

   Callback gets result info, not deleted doc [OK]

Hint: Callback second param is result info, not deleted doc [OK]

Common Mistakes:

• Expecting deleted document in callback
• Using deleteMany when only one document needed
• Assuming deleteOne does not accept callbacks

5. You want to delete all documents where the field active is false, but only if the user confirms. Which Express code snippet correctly handles this with error checking?

hard

A. Model.deleteMany({ active: false }, (err, res) => {
if (err) throw err;
console.log(res);
});

B. if(confirm) {
Model.deleteMany({ active: false })
.then(res => console.log(`${res.deletedCount} deleted`))
.catch(err => console.error(err));
}

C. if(confirm) {
Model.deleteOne({ active: false })
.then(res => console.log(res))
.catch(err => console.error(err));
}

D. Model.deleteMany({ active: false })
.then(res => console.log(res.deletedCount))
.catch(err => console.error(err));

Solution

1. Step 1: Check user confirmation before deleting

   if(confirm) { Model.deleteMany({ active: false }) .then(res => console.log(`${res.deletedCount} deleted`)) .catch(err => console.error(err)); } uses an if(confirm) check to ensure deletion only happens after user confirmation.

2. Step 2: Verify deletion and error handling

   It uses deleteMany to delete all matching documents, logs the count, and catches errors properly.

3. Final Answer:

   if(confirm) { Model.deleteMany({ active: false }) .then(res => console.log(`${res.deletedCount} deleted`)) .catch(err => console.error(err)); } -> Option B

4. Quick Check:

   Confirm before delete, handle errors [OK]

Hint: Check confirm before deleteMany, handle errors in promise [OK]

Common Mistakes:

• Using deleteOne instead of deleteMany for multiple docs
• Not checking user confirmation before deleting
• Throwing errors instead of catching them