Allow EntityRepository::FindBy to accept a Criteria object or array. #6136

New Issue

admin · 2026-01-22T15:27:27+01:00

admin commented

2026-01-22 15:27:27 +01:00

Originally created by @PyRowMan on GitHub (Dec 14, 2018).

Feature Request

In order to do advanced where clauses select (greaterThan, lesserThan, equals...).

Would it be possible to allow the method EntityRepository::FindBy to take a Criteria object OR an array of params.

It would be easier to perform some advanced where clauses.

Q	A
New Feature	yes
RFC	yes
BC Break	no

Summary

Since I don't usually work inside the doctrine project, I don't really know what are the impacts of this request. I saw that there is one or two interfaces to modify, and some recovering parameter way, but this is only for the MySQL driver.

Originally created by @PyRowMan on GitHub (Dec 14, 2018). ### Feature Request In order to do advanced where clauses select (greaterThan, lesserThan, equals...). Would it be possible to allow the method EntityRepository::FindBy to take a Criteria object OR an array of params. It would be easier to perform some advanced where clauses. | Q | A |------------ | ------ | New Feature | yes | RFC | yes | BC Break | no #### Summary Since I don't usually work inside the doctrine project, I don't really know what are the impacts of this request. I saw that there is one or two interfaces to modify, and some recovering parameter way, but this is only for the MySQL driver.

admin added the Improvement label 2026-01-22 15:27:27 +01:00

admin closed this issue

2026-01-22 15:27:27 +01:00

admin commented

2026-01-22 15:27:28 +01:00

@Ocramius commented on GitHub (Dec 14, 2018):

I'd rather say that a separate findByCriteria() would be preferable, over having a union type.

@Ocramius commented on GitHub (Dec 14, 2018): I'd rather say that a separate `findByCriteria()` would be preferable, over having a union type.

admin commented

2026-01-22 15:27:28 +01:00

@dlgoodchild commented on GitHub (Aug 12, 2020):

I've just come across this from wondering how to specify operators for the findBy criteria array.

I think having a findByCriteria and findOneByCriteria would be a great addition here.

@dlgoodchild commented on GitHub (Aug 12, 2020): I've just come across this from wondering how to specify operators for the `findBy` criteria array. I think having a `findByCriteria` and `findOneByCriteria` would be a great addition here.

admin commented

2026-01-22 15:27:29 +01:00

@Ocramius commented on GitHub (Aug 12, 2020):

Are you perhaps looking for https://github.com/doctrine/orm/blob/v2.7.3/lib/Doctrine/ORM/EntityRepository.php#L281?

@Ocramius commented on GitHub (Aug 12, 2020): Are you perhaps looking for https://github.com/doctrine/orm/blob/v2.7.3/lib/Doctrine/ORM/EntityRepository.php#L281?

admin commented

2026-01-22 15:27:29 +01:00

@dlgoodchild commented on GitHub (Aug 12, 2020):

Mmm that seems to be quite different to the find... methods and it recieves only a single Criteria object (and returns a Collection), seems a bit inconsistent and I can't find the documentation covering matching.

@dlgoodchild commented on GitHub (Aug 12, 2020): Mmm that seems to be quite different to the `find...` methods and it recieves only a single Criteria object (and returns a Collection), seems a bit inconsistent and I can't find the documentation covering `matching`.

admin commented

2026-01-22 15:27:29 +01:00

@beberlei commented on GitHub (Dec 6, 2020):

Yes EntityRepository::matching is the solution here. Different API is needed so you can support lazy and subfiltering.

@beberlei commented on GitHub (Dec 6, 2020): Yes `EntityRepository::matching` is the solution here. Different API is needed so you can support lazy and subfiltering.

admin referenced this issue

2026-01-22 16:05:39 +01:00

[PR #6136] [DX] Add details about invalid Connection passed at creation of EntityManager. #9861

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#6136