Merged
Conversation
Supported since ext-mongodb 1.2 mongodb/mongo-php-driver#336
* Add test for memory duplicate * Fix persist a removed document * Update tests to ensure the document is inserted, not upserted
…#2739) And fix `$geoNear` stage with empty query
Bumps [doctrine/.github](https://github.com/doctrine/.github) from 7.2.1 to 7.2.2. - [Release notes](https://github.com/doctrine/.github/releases) - [Commits](doctrine/.github@7.2.1...7.2.2) --- updated-dependencies: - dependency-name: doctrine/.github dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [doctrine/.github](https://github.com/doctrine/.github) from 7.2.1 to 7.2.2. - [Release notes](https://github.com/doctrine/.github/releases) - [Commits](doctrine/.github@7.2.1...7.2.2) --- updated-dependencies: - dependency-name: doctrine/.github dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…rine/dot-github-7.2.2 Bump doctrine/.github from 7.2.1 to 7.2.2
Merge 2.10.x into 2.11.x
Update documentation in Builder.php
…2750) When using write-concern="1" in XML mapping, the value was being cast to string, causing MongoDB to interpret it as a named write concern mode instead of a numeric level. This led to errors like: "No write concern mode named '1' found in replica set configuration". This commit ensures that numeric write concern values are properly cast to integers, while still allowing named modes such as "majority" to be used as strings. --------- Co-authored-by: Jérôme Tamarelle <jerome@tamarelle.net>
GromNaN
approved these changes
Apr 8, 2025
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
6 participants
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.
Release Notes for 2.11.0
Feature release (minor)
2.11.0
Documentation
Bug
$geoNearstage with empty query thanks to @GromNaN$textoperator in a aggregation with a filter thanks to @GromNaNFeature
$matchfrom pipeline builder thanks to @GromNaNEnhancement
spl_object_hashwithspl_object_idthanks to @GromNaN