[DOCS-3866] Docs should strongly advise against use of db.eval() Created: 04/Aug/14 Updated: 16/Mar/15 Resolved: 03/Oct/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Zola | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 9 years, 28 weeks, 2 days ago | ||||||||||||
| Description |
|
In general, using db.eval() or the $eval command is a Very Bad idea. The docs should discourage its use, and encourage the use of client-side operations (possibly with projection) instead. Problems with $eval:
|