* Add TokenType class
Co-authored-by: Alexander M. Turek <[email protected]>

* Deprecated Lexer constants in favour of TokenType

* Replace all Lexer::T_ occurrences with TokenType::T_

* Add upgrade note

* Fixed import Lexer => TokenType

* Fixed deprecation phpdoc

* Replaced int value with matching constant of TokenType

* Update src/Query/Lexer.php

---------

Co-authored-by: Alexander M. Turek <[email protected]>

Merge 2.18.x up into 2.19.x

… not yet fully completed on eagerLoadCollections

Merge 2.18.x up into 2.19.x

* 2.18.x:
  Fix Static Analysis folder reference (#11281)
  docs: recommend safer way to disable logging (#11269)
  Remove unused baseline entries
  Treat '0' as a legitimate trim char

After 2.17 (some?) EAGER fetched OneToMany associations stopped working, if they have multiple join columns. Loads for these associations will trigger a `MessingPositionalParameter` exception "Positional parameter at index 1 does not have a bound value".

This test case should reproduce this issue, so it can be fixed.

* 2.18.x:
  Backport QueryParameterTest (#11288)

Merge 2.18.x up into 2.19.x

`getAssociationMappedByTargetField()` returns `null` when called with
the owning side of an association.
This is undocumented and wrong because the phpdoc advertises a string as
a return type.

Instead, callers should ensure they are calling that method with an
inverse side.

Closes #11250

Deprecate invalid method call

Merge 2.18.x up into 2.19.x

* 2.18.x:
  PHPStan 1.10.59 (#11320)

* 2.18.x:
  Psalm 5.22.2 (#11326)

* 2.18.x:
  Bump CI workflows (#11336)
  Fix SchemaTool::getSchemaFromMetadata() uniqueConstraint without a predefined name (#11314)

* 2.18.x:
  Fix annotation

doctrine/rst-parser does not appear to support orphan metadata yet, and
renders it verbatim on the website.

Let's move this to the CI job.

Remove guides-specific markup

… exploration, and we only need the regression test.

…s no sense.

…ith-fetch-eager

[2.17.x] Failed getting entity with fetch eager property

…XnS7Xw9

Merge release 2.19.1 into 2.20.x

…ifier.

Page: https://www.doctrine-project.org/projects/doctrine-orm/en/2.19/reference/dql-doctrine-query-language.html#query-result-formats

Follow-up of #11359

The table I suggested is probably not working, since the text for each method is too long. And what I really wanted is to make it more *scanable*. So I tried boldfacing - if this doesn't work, I'll try something else.

Questions:

1. This section here is basically the same as https://www.doctrine-project.org/projects/doctrine-orm/en/2.10/reference/dql-doctrine-query-language.html#hydration-modes ! So I'll try to merge them (in another PR), OK? I think the list is a better format (more scanable) - since those methods all work the same, there's no need for a full-blown code sample for each, IMO.

2. `getSingleColumnResult()` is missing.

Minor code style fix in AbstractRemoteControl

Some of it seems related to the previous documentation build system,
some of it seems related to IntelliJ.

…te-key-eager-fetch-one

Do not use batch loading for collections with composite identifier

…yF2lMAL

Merge release 2.19.2 into 2.20.x

…11376)

* Improve lazy ghost performance by avoiding self-referencing closure.

Co-authored-by: Nicolas Grekas <[email protected]>

* update baselien

---------

Co-authored-by: Nicolas Grekas <[email protected]>

…socations. (#11380)

... in favor of https://www.doctrine-project.org/projects/doctrine-dbal/en/3.8/reference/types.html#reference

Page: https://www.doctrine-project.org/projects/doctrine-orm/en/2.19/reference/basic-mapping.html#doctrine-mapping-types

As announced in doctrine/dbal#6336 (comment) , the goal is to remove this duplicated type information from ORM and replace it with a link to DBAL.

In doctrine/dbal#6341 , I'm adding any detail which I'm deleting here to the DBAL.

* 2.19.x:
  [Documentation] Removing "Doctrine Mapping Types" ... (#11384)
  [GH-11185] Bugfix: do not use collection batch loading for indexBy assocations. (#11380)
  Improve lazy ghost performance by avoiding self-referencing closure. (#11376)

* 2.19.x:
  Remove unused variable (#11391)

See doctrine/collections#368 for the same
issue in doctrine/collections which has been fixed there.

The issue happens when using ->contains(). Running psalm emits

  > InvalidArgument - Argument 1 of Doctrine\ORM\PersistentCollection::contains
  > expects
  > TMaybeContained:fn-doctrine\common\collections\readablecollection::contains
  > as mixed, but … provided.

Solution: we should either not define @template TMaybeContained or
re-define the complete psalm docblock from ReadableCollection.

Repairing the docblock necessitates an update to the psalm baseline:
one "known issue" is no longer an issue and thus removed.

[Documentation] Query Result Formats

Fix psalm errors: remove override of template type

Page: https://www.doctrine-project.org/projects/doctrine-orm/en/2.19/reference/dql-doctrine-query-language.html#query-result-formats

As announced in #11372 (comment), I merged the (mostly) identical sections.

* I changed the `const`s from `Query` to `AbstractQuery`
* I deleted this - mainly cause I didn't find a nice place for it:
    > In parentheses are the constants of the ``Query`` class which you can use with the
general-purpose method ``Query::execute(array $params = [], $hydrationMode = Query::HYDRATE_OBJECT)``.

[Documentation] Merging "Query Result Formats" with "Hydration Modes"

* Improve getClassMetadata phpdoc

* Update baseline

* 2.19.x:
  Fix BIGINT validation (#11414)
  Fix templated phpdoc return type (#11407)
  [Documentation] Merging "Query Result Formats" with "Hydration Modes"
  Fix psalm errors: remove override of template type
  Update dql-doctrine-query-language.rst
  Adding `NonUniqueResultException`
  [Documentation] Query Result Formats

fix(docs): typo

EAGER fetch mode ignores orderBy as of changes introduced with #8391

Fixes #11163
Fixes #11381

Bugfix: respect orderBy for fetch EAGER mode

Previously it didn't cleanup anything as long as the iteration hasn't reached the final row.

Co-authored-by: Oleg Andreyev <[email protected]>

Changed capitalized column names to lowercase for consistency. Other occurances of column names mentioned as lowercase several times at this same page.

Update association-mapping.rst

…ted.

If the entity gets reloaded from database before the deletions are
executed UnitOfWork needs to be able to return the original instance in
REMOVED state.

…ty-map

Prevent creation of new MANAGED entity instance by reloading REMOVED entity from database

Remove unused test group

Fix deprecation layer of Doctrine\ORM\ORMException

…fraK93L

Merge release 2.19.5 into 2.20.x

Upgrade codecov/codecov-action

Bumps [doctrine/.github](https://github.com/doctrine/.github) from 3.0.0 to 5.0.1.
- [Release notes](https://github.com/doctrine/.github/releases)
- [Commits](doctrine/.github@3.0.0...5.0.1)

---
updated-dependencies:
- dependency-name: doctrine/.github
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

…9.x/doctrine/dot-github-5.0.1

Bump doctrine/.github from 3.0.0 to 5.0.1

Bumps [ramsey/composer-install](https://github.com/ramsey/composer-install) from 2 to 3.
- [Release notes](https://github.com/ramsey/composer-install/releases)
- [Commits](ramsey/composer-install@v2...v3)

---
updated-dependencies:
- dependency-name: ramsey/composer-install
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* 2.19.x:
  Bump ramsey/composer-install from 2 to 3 (#11442)
  Bump doctrine/.github from 3.0.0 to 5.0.1
  Upgrade codecov/codecov-action

* 2.19.x:
  Psalm 5.24.0 (#11467)
  PHPStan 1.11.1 (#11466)
  Test with actual lock modes (#11465)
  Backport test for Query::setLockMode() (#11463)

…f fetch-mode EAGER and WITH condition.

This fixes a bug that arises when 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).

Fixes #11128

Co-Authored-By: Albert Prat <[email protected]>

One has been deprecated in favor of the other.

docs: update EntityManager#transactional to EntityManager#wrapInTransaction

Consider usage of setFetchMode when checking for simultaneous usage of fetch-mode EAGER and WITH condition

Fix cloning entities

It will handle caching for us.