[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:
Related
is related to SERVER-12051 autoIndexId=false allowed on non capp... Closed
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: DOCS-3521 db.createCollection() autoIndexId option not only for capped
Branch: master
https://github.com/mongodb/docs/commit/daa018884d4ff997136aded3582aeb2adf04a993

Generated at Thu Feb 08 07:45:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.