Find Options (Post-Matching Processing)
Description
These options are applied as part of a post-processing step after matching objects are found in the database (find stage) but before the data is returned to the client.
This process is designed to:
1. Reduce data transfer size by removing unnecessary fields or selecting only the required ones.
2. Customize results by transforming objects to meet specific requirements.
This optimization improves both performance and result usability, ensuring the client receives precisely the needed data in a compact form.
Execution Stack
transformexcludeselect
Operators
select
Selects only specific fields to include in the final object.
// Original Object
{
name: "John Doe",
email: "john@example.com",
age: 30,
status: "active"
}
// Find Options
{
select: ["name", "email"]
}
// Result
{
name: "John Doe",
email: "john@example.com"
}
exclude
Excludes specific fields from the object, removing unwanted data.
// Original Object
{
name: "John Doe",
email: "john@example.com",
age: 30,
status: "active"
}
// Find Options
{
exclude: ["name"]
}
// Result
{
email: "john@example.com",
age: 30,
status: "active"
}
transform
Applies a custom updater function to modify the object.
// Original Object
{
name: "John Doe",
email: "john@example.com",
age: 30,
status: "active"
}
// Find Options
{
transform: (doc) => {
doc.name = doc.name.toUpperCase();
return doc;
}
}
// Result
{
name: "JOHN DOE",
email: "john@example.com",
age: 30,
status: "active"
}
Combined Example
Using all operators together to demonstrate the execution stack.
// Original Object
{
name: "John Doe",
email: "john@example.com",
age: 30,
status: "active"
}
// Find Options
{
transform: (doc) => {
doc.newField = "added";
doc.status = "inactive";
return doc;
},
exclude: ["email", "newField"],
select: ["name", "status"]
}
// Execution Steps:
1. transform:
{
name: "John Doe",
email: "john@example.com",
age: 30,
status: "inactive",
newField: "added"
}
2. exclude:
{
name: "John Doe",
age: 30,
status: "inactive"
}
3. select:
{
name: "John Doe",
status: "inactive"
}
// Final Result:
{
name: "John Doe",
status: "inactive"
}
Edge Cases and Important Notes
Nested Paths with Arrays
When using dotted paths or array paths in select / exclude,
paths do not traverse through arrays.
If a path segment points to an array (and the next segment is not a numeric index),
the field is omitted from the result:
// Original Object
{
users: [
{ name: "Alice", age: 30 },
{ name: "Bob", age: 25 }
]
}
// Find Options
{
select: ["users.name"]
}
// Result - the "users" field is omitted entirely
{}
To work with array elements, use paths with specific indices:
{
select: ["users.0.name"] // or [["users", "0", "name"]]
}
// Result
{
users: {
"0": {
name: "Alice"
}
}
}
Empty Select vs Empty Exclude
select: []returns an empty object{}exclude: []returns the original object unchanged
Transform Function Return Value
The transform function must return the resulting object. It can either:
- Modify and return the object (creates a new reference)
- Mutate in place and return the same object
// Option 1: Return new object
{ transform: (doc) => ({ ...doc, modified: true }) }
// Option 2: Mutate and return the same reference
{ transform: (doc) => { doc.modified = true; return doc; } }
Warning: returning undefined does not keep the original object. The result becomes undefined (or an empty object {} when select is used):
// WRONG - do not do this
{ transform: (doc) => { doc.modified = true; } }
Select and Exclude Interaction
When both select and exclude are used:
excludeis applied first (removes fields from the object)selectis applied second (creates object with only selected fields from the remaining)
// Original: { a: 1, b: 2, c: 3, d: 4 }
{
exclude: ["b"], // Step 1: { a: 1, c: 3, d: 4 }
select: ["a", "c"] // Step 2: { a: 1, c: 3 }
}
The full execution order is always: transform -> exclude -> select.
Non-Existent Paths
- Selecting non-existent paths omits the field from the result (no
undefinedplaceholder is created) - Excluding non-existent paths has no effect (no error thrown)