Update doctrine/orm from v2.6.3 to 2.9.4#48
Open
violinist-bot wants to merge 1 commit intodpeuscher:masterfrom
Open
Update doctrine/orm from v2.6.3 to 2.9.4#48violinist-bot wants to merge 1 commit intodpeuscher:masterfrom
violinist-bot wants to merge 1 commit intodpeuscher:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
If you have a high test coverage index, and your tests for this pull request are passing, it should be both safe and recommended to merge this update.
Updated packages
Some times an update also needs new or updated dependencies to be installed. Even if this branch is for updating one dependency, it might contain other installs or updates. All of the updates in this branch can be found here.
List of updated packages
Changelog
Here is a list of changes between the version you use, and the version this pull request updates to:
@returntype next to#[ReturnTypeWillChange]fieldsto Index (#8830)UNIQUE INDEXto generated SQL schemadefault(#8671)notnullfield import (#8649)tmpdb_toprivileged_dbin test config and TestUtilTfrom class metadata (#8398)datetime_immutableDBAL type for\DateTimeImmutableinstance parameters (#8328)getIterable()totoIterable()(part 2) (#8293)getIterable()on AbstractQuery (#7885)mysqliis used with discriminator column that is not a string (#8055)clear.WhereInWalkeris being usedWhereInWalkerrunPersisterHelperto figure out identifier typesPersisterHelper#getTypeOfField()array return typeDoctrine\ORM\Mapping\ClassMetadataInfo#getTypeOfColumn()Paginatorto theWhereInWalker, which already has access to class metadata for the root of the selection (and can reliably detect the root of the selection too)WHERE IN(?)queries before binding parametersUnitOfWork#getSingleIdentifierValue()still being called when not specifying the type of a DQL parameter being bound viaDoctrine\ORM\Query#setParameter():UnitOfWork#getSingleIdentifierValue()should not be called for a well specified parameter typeThis is an automated pull request from Violinist: Continuously and automatically monitor and update your composer dependencies. Have ideas on how to improve this message? All violinist messages are open-source, and can be improved here.