Merge release 2.20.3 into 2.21.x #11929
Merged
Conversation
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
[DDC-551] fix, add filter support in oneToOne relation 2.20.x
…ctor This fixes a bug that arises when using Pagination and an entity relation is mapped with fetch-mode EAGER but setFetchMode LAZY (or anything that is not EAGER) has been used on the query. If the query use WITH condition, an exception is incorrectly raised (Associations with fetch-mode=EAGER may not be using WITH conditions). The class LimitSubqueryOutputWalker clones the query, but not its parameters and hints, so the generated subquery does not know that fetch-mode has been overridden. Fixes #11741
Clone query hints and parameters in `LimitSubqueryOutputWalker` constructor
Fix DQL example with composite key
update message to use attribute instead of annotation
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] <[email protected]>
…0.x/doctrine/dot-github-7.2.2 Bump doctrine/.github from 7.2.1 to 7.2.2
…-attribute Update message of `ORMInvalidArgumentException`
They don't have a special meaning, and are rendered like this: <strong>*REQUIRED</strong>*.
Avoid triple stars
Fix docs typo (nulable -> nullable)
Co-authored-by: Grégoire Paris <[email protected]>
These URLs are meant as identifiers rather than actual urls intended to be used to perform an HTTP request.
Fix URL's in xml-mapping.rst
Add more detailed caveats for using the Collection filtering API
The old proxy implementation of doctrine/common was triggered by public methods rather than access to properties (making public properties unsupported in entities), so tests could use public instance properties to track the state of postLoad lifecycle callbacks without triggering the proxy initialization when reading that state (which then changes the state of triggering the postLoad callback). As the new proxy implementation hooks into properties instead, the tests now use a static method (ensuring it is reset properly before loading the instance for which we care about the tracking) instead of an instance property.
PostLoad listeners might initialize values for transient properties, so the proxy should not skip initialization when using transient properties. Co-authored-by: Nicolas Grekas <[email protected]>
Fix the initialization of lazy-ghost proxies with postLoad listeners
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.
Release Notes for 2.20.3
2.20.x bugfix release (patch)
2.20.3
Bug
LimitSubqueryOutputWalkerconstructor thanks to @aprat84Documentation
Code Style
Test Suite
CI
Improvement
ORMInvalidArgumentExceptionthanks to @lacatoire