Bump doctrine/orm from 2.16.2 to 3.1.3

[dependabot[bot]]

Bumps doctrine/orm from 2.16.2 to 3.1.3.

Release notes

Sourced from doctrine/orm's releases.

3.1.3

Release Notes for 3.1.3

3.1.3

• Total issues resolved: 0
• Total pull requests resolved: 6
• Total contributors: 6

Bugfixes

• 11430: Fix deprecation layer of Doctrine\ORM\ORMException thanks to @​W0rma
• 11428: Prevent creation of new MANAGED entity instance by reloading REMOVED entity from database thanks to @​xificurk
• 11422: Bugfix: respect orderBy for fetch EAGER mode thanks to @​tomasz-ryba
• 11101: fix: always cleanup in AbstractHydrator::toIterable() thanks to @​simPod

Test Suite

• 11429: Remove unused test group thanks to @​SenseException

Documentation

• 11420: fix(docs): typo thanks to @​tyteen4a03

3.1.2

Release Notes for 3.1.2

3.1.2

• Total issues resolved: 0
• Total pull requests resolved: 4
• Total contributors: 4

Bug

• 11415: Revert "SchemaValidator: Changing mapping of BIGINT to string|int" thanks to @​derrabus
• 11399: SchemaValidator: Changing mapping of BIGINT to string|int thanks to @​ThomasLandauer

Documentation

• 11413: docs: update PHP version in doc thanks to @​Nayte91

Static Analysis

• 11408: Fix fromMappingArray definition thanks to @​VincentLanglet

... (truncated)

Upgrade guide

Sourced from doctrine/orm's upgrade guide.

Upgrade to 3.1

Deprecate Doctrine\ORM\Mapping\ReflectionEnumProperty

This class is deprecated and will be removed in 4.0. Instead, use Doctrine\Persistence\Reflection\EnumReflectionProperty from doctrine/persistence.

Deprecate passing null to ClassMetadata::fullyQualifiedClassName()

Passing null to Doctrine\ORM\ClassMetadata::fullyQualifiedClassName() is deprecated and will no longer be possible in 4.0.

Deprecate array access

Using array access on instances of the following classes is deprecated:

• Doctrine\ORM\Mapping\DiscriminatorColumnMapping
• Doctrine\ORM\Mapping\EmbedClassMapping
• Doctrine\ORM\Mapping\FieldMapping
• Doctrine\ORM\Mapping\JoinColumnMapping
• Doctrine\ORM\Mapping\JoinTableMapping

Upgrade to 3.0

BC BREAK: Calling ClassMetadata::getAssociationMappedByTargetField() with the owning side of an association now throws an exception

Previously, calling Doctrine\ORM\Mapping\ClassMetadata::getAssociationMappedByTargetField() with the owning side of an association returned null, which was undocumented, and wrong according to the phpdoc of the parent method.

If you do not know whether you are on the owning or inverse side of an association, you can use Doctrine\ORM\Mapping\ClassMetadata::isAssociationInverseSide() to find out.

BC BREAK: Doctrine\ORM\Proxy\Autoloader no longer extends Doctrine\Common\Proxy\Autoloader

Make sure to use the former when writing a type declaration or an instanceof check.

Minor BC BREAK: Changed order of arguments passed to OneToOne, ManyToOne and Index mapping PHP attributes

To keep PHP mapping attributes consistent, order of arguments passed to above attributes has been changed so $targetEntity is a first argument now. This change affects only non-named arguments usage.

BC BREAK: AUTO keyword for identity generation defaults to IDENTITY for PostgreSQL when using doctrine/dbal 4

When using the AUTO strategy to let Doctrine determine the identity generation mechanism for an entity, and when using doctrine/dbal 4, PostgreSQL now uses IDENTITY instead of SEQUENCE or SERIAL.

... (truncated)

Commits

• 8ca99fd Merge pull request #11433 from greg0ire/3.1.x
• 2d8e466 Merge remote-tracking branch 'origin/2.19.x' into 3.1.x
• 94986af Merge pull request #11430 from W0rma/fix-deprecation-layer-orm-exception
• ad5c8e4 Make test compatible with PHP 7.1
• c363f55 Fix deprecation layer
• c973a62 Merge pull request #11429 from SenseException/unused-test-group
• 8d34460 Merge pull request #11428 from xificurk/keep-removed-entity-in-identity-map
• 4e335f4 Remove unused test group
• bb36d49 Keep entities in identity map until the scheduled deletions are executed.
• 2b81a8e Merge pull request #11426 from nasimic/patch-1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)