Repository navigation
[mongodb] Document duplicate keys behavior in BSON documents - #50
Merged
Merged
Conversation
GromNaN
changed the title
This was referenced Oct 23, 2026
GromNaN
force-pushed
the
docs/mongodb-bson-duplicate-keys
branch
from
October 23, 2026 17:52
8faef9a to
203f694
Compare
This file contains hidden or 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
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.
The driver does not validate duplicate keys in BSON documents. This documents how
Documenthandles them: iteration and the JSON conversions keep every element,get()andoffsetGet()return the first value, andtoPHP()keeps the last value.The existing duplicate keys warning is updated to say that this behavior is covered by tests, but applications should still avoid duplicate keys.