GODRIVER-3475 Correct CreateCollection and CreateView docs. #1933
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
API Change ReportNo changes found! |
matthewdale
force-pushed
the
godriver3475-fix-createcoll-doc
branch
from
e05f1d1 to
d3e6168
Compare
matthewdale
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GODRIVER-3475
Summary
Update the
CreateCollectionandCreateViewdocs to reflect the new behavior of MongoDB version 7.0 and newer when the collection or view already exists.Background & Motivation
For MongoDB 7.0 and 8.0, the collection/view creation command no longer returns an error if an existing collection/view with the same name and configuration already exists. The following note on the "create" command was added for 7.0: