Update client eval page for 3.0

[divega]

Points to cover:

1. EF Core 3.0 does very limited client eval
2. Explicitly switching to client eval can be done, for example, with AsEnumerable, AsAsyncEnumerable, ToList, ToListAsync. Each has trade-offs.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: fd35b912-445c-e801-7f70-de73839db80d
• Version Independent ID: e558a081-5397-1e3f-1d58-abea3f72cad6
• Content: Client vs. Server Evaluation - EF Core
• Content Source: entity-framework/core/querying/client-eval.md
• Product: entity-framework
• Technology: entity-framework-core
• GitHub Login: @rowanmiller
• Microsoft Alias: divega

[smitpatel]

I updated to add AsEnumerable/AsAsyncEnumerable. Does anyone know any benefits of ToList/ToListAsync?

[AndriySvyryd]

No multiple evaluation when used again?

[roji]

Right, though I see people also doing ToList/ToListAsync even when enumerating only once, which is an anti-pattern (needless memory for buffering). We should ideally explain these nuances.

[ygoe]

ToList also fetches the data immediately. This may be necessary if the underlying cursor cannot stay open while doing other queries on the same connection, or if the enumeration being iterated will be changed (less relevant for database queries).