DEV Community

Cover image for 7 MongoDB Query Mistakes That Return the Wrong Results
VisuaLeaf
VisuaLeaf

Posted on • Originally published at visualeaf.com

7 MongoDB Query Mistakes That Return the Wrong Results

#mongodb #coding #software #database

MongoDB queries look simple. You type a field, give it a value, hit run, and you get your data back.

But just because a query runs without throwing an error doesn't mean it worked right. Sometimes you get a blank screen. Sometimes you get way too many records. Other times, the data looks fine at first glance, but it doesn't actually match what you asked for.

Most of these slip-ups happen for one basic reason: the query structure doesn't match the way the data actually sits in the database.

To show you what we mean, we’ll use a clinic database with a collection called visits. Here is what a typical document looks like:

JSON

{
  "_id": "6871b6f9c3f1d1a4c2a10001",
  "status": "completed",
  "visitDate": "2026-07-01T09:30:00.000Z",
  "patient": { "name": "Anna Keller", "age": 34 },
  "doctor": { "name": "Dr. James Carter", "specialty": "Cardiology" },
  "symptoms": ["cough", "fever"],
  "prescriptions": [
    { "name": "Ibuprofen", "active": false },
    { "name": "Paracetamol", "active": true }
  ],
  "invoice": { "paid": true, "method": "card", "total": 250 }
}
Enter fullscreen mode Exit fullscreen mode

You can run these examples right in the VisuaLeaf MongoDB Shell. Using visual tools makes a big difference because you can see exactly what MongoDB is returning in real time.

1. Forgetting the Curly Braces

This is just a quick typo, but it breaks things right away.

The Mistake:

db.visits.find(status: "completed")
Enter fullscreen mode Exit fullscreen mode

The Correct Query

MongoDB query examples showing common mistakes with $or, $in, arrays, dates, and text search in VisuaLeaf.

The find() tool always expects an object. Even if you are only looking for one specific thing, you still need to wrap that condition in curly braces {}.

2. Treating $or Like a Regular Object

This one trips a lot of people up because the broken version looks like it should work.

The Mistake:

db.visits.find({
  $or: {
    status: "completed",
    "invoice.paid": false
  }
})
Enter fullscreen mode Exit fullscreen mode

What is wrong:

$or expects an array of conditions, but this query gives it one object.
Enter fullscreen mode Exit fullscreen mode

The error will usually be something like:

MongoServerError: $or must be an array
Enter fullscreen mode Exit fullscreen mode

The Correct Query

MongoDB Shell query using $or with separate conditions, showing matching visit records in VisuaLeaf Table View.

The first query is wrong because $or needs an array, not one regular object.

Each condition has to be written as its own object inside [].

The corrected query returns visits where the status is pending or completed.

3. Querying Nested Fields Like They Are Flat

MongoDB documents often have fields inside other fields.

In our visits collection, doctor is an object:

doctor: {
  name: "Dr. Michael Brown",
  specialization: "Neurology"
}
Enter fullscreen mode Exit fullscreen mode

Query to avoid:

db.visits.find({
  doctor: "Neurology"
})
Enter fullscreen mode Exit fullscreen mode

This asks MongoDB to find a doctor field that is exactly "Neurology".

But doctor is not a string. It is an object.

Better query:

db.visits.find({
  "doctor.specialization": "Neurology"
})
Enter fullscreen mode Exit fullscreen mode

MongoDB query for a nested doctor.specialization field shown in VisuaLeaf Tree View.

The dot tells MongoDB to go inside the doctor object and check the specialization field.

So instead of asking:

Is the whole doctor field equal to Neurology?

you are asking:

Is the doctor’s specialization Neurology?

4. Typing the Same Field Twice

Say you want to find visits with doctors from Cardiology or Dermatology.

Query to avoid:

db.visits.find({
  "doctor.specialization": "Cardiology",
  "doctor.specialization": "Dermatology"
})
Enter fullscreen mode Exit fullscreen mode

Better query:

MongoDB Shell query using $in to search visits by multiple values in the same field, with results shown in VisuaLeaf Table View.

In JavaScript and MongoDB, you should not reuse the same key within a single object.

If you type "doctor.specialization" twice, the second value can overwrite the first one. So MongoDB may only search for Dermatology.

If one field can match more than one value, use $in.

5. Treating Dates Like Plain Text

Dates can look like regular text, but in MongoDB they are often stored as real Date values.

In our visits collection, the invoice date is stored inside the invoice object:

invoice: {
  issuedAt: ISODate("2026-05-18T10:15:00Z")
}
Enter fullscreen mode Exit fullscreen mode

So this query will not work as expected:

db.visits.find({
  "invoice.issuedAt": "2026-05-18"
})
Enter fullscreen mode Exit fullscreen mode

This searches for a string, not a Date, so it will usually return nothing.

Better query:

MongoDB Shell query in VisuaLeaf using $gte and $lt with new Date() to find invoices issued on May 18, 2026, with the matching result shown in Table View.

This returns invoices created on May 18, 2026.

The range matters because dates usually include time. A visit at 1:15 PM is still on May 18, but it is not equal to midnight.

So instead of asking:

Is the date exactly "2026-05-18"?

you are asking:

Is the date on or after May 18 and before May 19?

6. Expecting Text Search to Work Automatically

MongoDB does not search text like Google by default.

In our visits collection, the doctor name is stored like this:

doctor: {
  fullName: "Dr. Michael Brown"
}
Enter fullscreen mode Exit fullscreen mode

So this query will not work:

db.visits.find({
  "doctor.fullName": "Michael"
})
Enter fullscreen mode Exit fullscreen mode

This searches for an exact value. MongoDB checks if doctor.fullName is exactly "Michael".

But the real value is "Dr. Michael Brown".

Better setup:

For text search, you need to create a text index first:

db.visits.createIndex({
  "doctor.fullName": "text"
})
Enter fullscreen mode Exit fullscreen mode

Then you can search inside the text field:

MongoDB Shell query in VisuaLeaf using $text search for “Michael,” with the matching doctor name shown in Table View.

Now MongoDB can search for the word Michael inside the indexed field.

The important part is this:

$text search does not work unless the collection has a text index.

7. Reading $or Logic Backwards

This query runs fine, but it is easy to read it *the wrong way*:

db.visits.find({
  status: "completed",
  $or: [
    { "doctor.specialization": "Neurology" },
    { "invoice.paymentStatus": "unpaid" }
  ]
})
Enter fullscreen mode Exit fullscreen mode

This does not mean:

completed OR Neurology OR unpaid
Enter fullscreen mode Exit fullscreen mode

It actually means:

completed AND (Neurology OR unpaid)
Enter fullscreen mode Exit fullscreen mode

Because status is outside the $or block, MongoDB treats it as required.

So MongoDB first looks for visits where status is completed. Then, from those visits, it checks if the doctor is specialized in Neurology or the invoice is unpaid.

If you want all three conditions to be part of the OR logic, move status inside the $or array.

Better query:

db.visits.find({
  $or: [
    { status: "completed" },
    { "doctor.specialization": "Neurology" },
    { "invoice.paymentStatus": "unpaid" }
  ]
})
Enter fullscreen mode Exit fullscreen mode

Now the query means:

completed OR Neurology OR unpaid
Enter fullscreen mode Exit fullscreen mode

Same fields. Different structure. Different result.

Side-by-side VisuaLeaf MongoDB Shell screenshot comparing two $or queries, showing how moving status inside the $or array returns more matching documents.

One More Thing to Do before Using Your Query

A MongoDB query is only as good as your understanding of the underlying document structure.

Before you spend hours rewriting a broken query, do one simple thing: Open a single raw document from your collection.

  • Look closely at the exact spelling of field names.
  • Check the data types (Are numbers stored as strings? Are dates stored as objects?).
  • Map out your nested objects.

This is exactly where a visual tool like VisuaLeaf saves the day. Instead of guessing from your code editor, you can test your queries inside the built-in shell and instantly toggle over to the Table View or Tree View to see exactly how your documents are laid out in real-time. No more guessing.

Top comments (0)