[DOCS-3521] db.createCollection() page incorrectly lists autoIndexId option as capped-specific Created: 02/Jun/14 Updated: 16/Mar/15 Resolved: 02/Jun/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | J Rassi |
| 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, 37 weeks, 2 days ago | ||||||||
| Description |
|
The "autoIndexId" option to the "create" command affects both capped collections and non-capped collections. It is documented correctly on the "create" command page, but is incorrectly documented as only affecting capped collections on the db.createCollection() page. |
| Comments |
| Comment by Githook User [ 02/Jun/14 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |