MongoDB Academy · Aula

Projeções por inclusão versus exclusão

Selecione ou suprima campos específicos nos resultados das consultas e entenda por que não é possível combinar inclusão e exclusão em uma única projeção.

Projeções por inclusão versus exclusão é uma aula grátis de MongoDB Academy no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de MongoDB Academy, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de MongoDB Academy inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

What Is a Projection?

A projection is the second argument to find() or findOne() that tells MongoDB which fields to include or exclude from the result. Instead of returning the entire document, you specify exactly the fields you need. This reduces bandwidth, decreases memory usage in your application, and keeps API responses lean. Projections are one of the simplest and most impactful query optimisations available.

Inclusion Mode: Specify What to Return

In inclusion mode, you list the fields you want to receive and set their value to 1. MongoDB returns only those fields plus _id (which is included by default). This is the most common form of projection because it explicitly declares the fields your query depends on, making the intent clear to anyone reading the code.

// Return only name and email — everything else is excluded
const user = await db.collection('users').findOne(
  { email: 'alice@example.com' },
  { projection: { name: 1, email: 1 } }
);
// Result: { _id: ObjectId('...'), name: 'Alice', email: 'alice@example.com' }

Excluding _id From Results

The _id field is always included in inclusion projections unless you explicitly exclude it. Set _id: 0 alongside inclusion fields to suppress it. This is useful when building API responses that use a different identifier field, or when you want to avoid leaking internal MongoDB IDs to clients.

// Include name and email but suppress _id
const user = await db.collection('users').findOne(
  { email: 'alice@example.com' },
  { projection: { _id: 0, name: 1, email: 1 } }
);
// Result: { name: 'Alice', email: 'alice@example.com' }
// _id is not present

Exclusion Mode: Specify What to Omit

In exclusion mode, you set fields to 0 to remove them from the result. Every other field is returned. This is useful when you want almost all fields but need to suppress a few sensitive or large ones—for example, hiding a passwordHash field from query results in a general-purpose user query.

// Return all user fields EXCEPT passwordHash and internalNotes
const user = await db.collection('users').findOne(
  { email: 'alice@example.com' },
  { projection: { passwordHash: 0, internalNotes: 0 } }
);
// Result: everything except passwordHash and internalNotes

Cannot Mix Inclusion and Exclusion

MongoDB does not allow mixing inclusion (1) and exclusion (0) fields in a single projection, except for the _id field. Attempting to do so results in a Projection cannot have a mix of inclusion and exclusion fields error. Choose one mode per query. The only legal combination is inclusion fields (1) with _id: 0.

// VALID: inclusion mode with _id suppressed
{ projection: { name: 1, email: 1, _id: 0 } }

// VALID: exclusion mode
{ projection: { passwordHash: 0, secret: 0 } }

// INVALID: mixing 1 and 0 (throws an error)
// { projection: { name: 1, passwordHash: 0 } }  <- ERROR

Projections in find() vs Aggregation

In find(), projection is the second argument. In the aggregation pipeline, you use the $project stage, which supports the same inclusion/exclusion syntax plus computed fields and expressions. Both behave the same way with respect to the cannot-mix rule, but $project is more powerful because it can rename fields and add calculated values.

// find() projection
db.users.find({}, { name: 1, email: 1, _id: 0 });

// Equivalent in aggregation with $project
db.users.aggregate([
  { $project: { name: 1, email: 1, _id: 0 } }
]);

Projections and Covered Queries

A covered query is a query where both the filter fields and the projection fields are entirely within a single index. MongoDB can answer a covered query from the index alone without reading the actual document from disk. Projections are essential for covered queries: if you project a field not in the index, MongoDB must fetch the document, breaking the coverage benefit.

// Index on { email: 1, name: 1 }
db.users.createIndex({ email: 1, name: 1 });

// Covered query — filter + projection both satisfied by the index
db.users.find(
  { email: 'alice@example.com' },
  { name: 1, email: 1, _id: 0 }  // _id must be excluded for full coverage
).explain('executionStats');
// Look for 'totalDocsExamined: 0' in the output

Projections With Mongoose

In Mongoose, you can pass a projection string or object to .select(). A space-separated string with + for inclusion and - for exclusion is common. Fields marked with select: false in the schema (like passwordHash) are excluded from results by default and must be explicitly included with +passwordHash.

// Mongoose: string projection (+ include, - exclude)
const users = await User.find({}).select('name email -_id');

// Object projection
const user = await User.findOne({ email: 'a@b.com' }).select({ name: 1, email: 1, _id: 0 });

// Schema-level default exclusion
const userSchema = new mongoose.Schema({
  email: String,
  passwordHash: { type: String, select: false }  // excluded by default
});

Projection Performance Benefits

Projections improve performance in three ways: (1) they reduce the amount of data read from disk when the projection aligns with an index; (2) they reduce network bandwidth between the MongoDB server and your application; (3) they reduce the amount of memory your application must allocate to hold query results. For large documents or high-throughput APIs, projections can reduce response size by 80% or more.

Projecting Computed Values in Aggregation

The $project stage in aggregation goes beyond simple inclusion/exclusion. You can compute new fields using expressions—for example, concatenating strings, performing arithmetic, or extracting parts of a date. This lets you transform the shape of documents server-side before sending results to the application, reducing client-side processing.

db.orders.aggregate([
  {
    $project: {
      orderId: '$_id',
      _id: 0,
      totalWithTax: { $multiply: ['$subtotal', 1.1] },  // computed field
      year: { $year: '$createdAt' }                       // date extraction
    }
  }
]);

Always Project Sensitive Fields Out

Never return sensitive fields like passwordHash, apiKey, ssn, or creditCardNumber in general-purpose queries. Use exclusion projections or schema-level select: false to ensure these fields never accidentally appear in API responses. Defence in depth means applying projections at the data layer as a backstop, even if the application already strips these fields from responses.

Quick Check

Test your understanding of MongoDB & NoSQL Databases concepts from this lesson.

Lesson Recap

In this lesson you learned: inclusion projections (value 1) return only listed fields, exclusion projections (value 0) return all fields except the listed ones, and you cannot mix inclusion and exclusion except for _id: 0 with inclusion fields. Next up we explore projecting nested fields and arrays using dot notation and $slice.

Perguntas Frequentes

A aula “Projeções por inclusão versus exclusão” é grátis?

Sim — o texto completo de “Projeções por inclusão versus exclusão” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de MongoDB Academy, atualize para CoddyKit PRO. O curso de MongoDB Academy inclui 4 aulas no total.

O que vou aprender em “Projeções por inclusão versus exclusão”?

Selecione ou suprima campos específicos nos resultados das consultas e entenda por que não é possível combinar inclusão e exclusão em uma única projeção. Você pratica MongoDB Academy com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar MongoDB Academy?

Nenhuma experiência prévia é necessária. MongoDB Academy no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.

Quanto tempo leva a aula “Projeções por inclusão versus exclusão”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de MongoDB Academy?

Sim. Cada aula de MongoDB Academy inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

Projeções por inclusão versus exclusão
Projetando campos aninhados e de matrizes
As projeções de matrizes $ e $elemMatch
Práticas recomendadas de projeção para respostas de API

← Voltar para MongoDB Academy