Merge 3.4.x up into 4.0.x #11841
Merged
Merge 3.4.x up into 4.0.x #11841
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
It unlocks autocompletion and validation in some IDEs.
Add missing generated option to documentation
Bumps [doctrine/.github](https://github.com/doctrine/.github) from 6.0.0 to 7.1.0. - [Release notes](https://github.com/doctrine/.github/releases) - [Commits](doctrine/.github@6.0.0...7.1.0) --- updated-dependencies: - dependency-name: doctrine/.github dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…ions/2.20.x/doctrine/dot-github-7.1.0 Bump doctrine/.github from 6.0.0 to 7.1.0
This fixes a bug that occurs when calling setHint(Query::HINT_READ_ONLY, false) from a query object. UnitOfWork checks if this hint exists without considering the value passed as second argument. Handling the second parameter improves consistency with documentation. https://www.doctrine-project.org/projects/doctrine-orm/en/2.20/reference/improving-performance.html#read-only-entities
…rtFieldsWhereDeclared`
…ts-boolean-value Check hint value before considering instance read-only
Merge 2.20.x up into 3.3.x
….4.x_xx7XyUCl Merge release 3.3.1 into 3.4.x
Previously, when using a custom naming strategy, explicitly declaring a JoinColumn required specifying the referencedColumnName always as it would default to id no matter the naming strategy. This PR changes it to be determines correctly. Ref doctrine#9558
Respect referencedColumnName defaults in custom naming strategies
* 3.3.x: Update working-with-objects.rst (doctrine#7553) changed confusing negative wording (doctrine#11775)
UPGRADE: Document QueryBuilder::setParameters() Type enforcement
These new issues are caused by doctrine/common 3.5.0, released 2 weeks ago.
Ignore deprecations from doctrine/common
…clared Fix fields of transient classes being considered duplicate with `reportFieldsWhereDeclared`
Nullability is not inherited from the PHP type. The change that enabled this feature was reversed in doctrine#8732.
Fix invalid enum value in array of enums
This will give a signal that there is work to be done without blocking other contributions by failing the build.
Display Doctrine deprecations when running PHPUnit
Merge 3.3.x up into 3.4.x
We should be using quoteSingleIdentifier(), assuming we only ever pass single identifiers here. See doctrine/dbal#6590
The bug related (doctrine#11694) and fixed mapping of sql column alias to field in entity (doctrine#11783) and invalidate cache [cache/persisted/entity|cache/persisted/collection] when sql filter changes
…exed-relation 11783 failure with indexed relation
Address quoteIdentifier() deprecation
[RFC] Expose QueryBuilder::getType
Bumps [doctrine/.github](https://github.com/doctrine/.github) from 7.1.0 to 7.2.1. - [Release notes](https://github.com/doctrine/.github/releases) - [Commits](doctrine/.github@7.1.0...7.2.1) --- updated-dependencies: - dependency-name: doctrine/.github dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…ions/2.20.x/doctrine/dot-github-7.2.1 Bump doctrine/.github from 7.1.0 to 7.2.1
….4.x_lzhu6IBq Merge release 3.3.2 into 3.4.x
[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 doctrine#11741
Clone query hints and parameters in `LimitSubqueryOutputWalker` constructor
Fix DQL example with composite key
This exception was dropped by mistake during a merge-up, and should be present until Doctrine officially supports property hooks.
Restore logic exception
Merge 2.20.x up into 3.3.x
Merge 3.3.x up into 3.4.x
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.
No description provided.