[SERVER-3107] For JS, add a findRO() that returns a read-only object, which can be much faster for certain cases Created: 16/May/11 Updated: 12/Jul/16 Resolved: 26/May/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Antoine Girbal | Assignee: | Antoine Girbal |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
if doing a find/read or find/insert in JS code, the JS object is considered writable. ) |
| Comments |
| Comment by Antoine Girbal [ 26/May/11 ] |
|
implemented as .readOnly() on cursor. |
| Comment by auto [ 26/May/11 ] |
|
Author: {u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}Message: |
| Comment by Scott Hernandez (Inactive) [ 16/May/11 ] |
|
What about find().readOnly() instead? |