mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
DDC-3346: findOneBy returns an object with partial collection for the properties with mapping oneToMany/Fetch Eager #4136
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Oct 10, 2014).
Originally assigned to: @Ocramius on GitHub.
Jira issue originally created by user adrienrusso:
findOneBy returns an object with partial collection for the properties with mapping oneToMany/Fetch Eager. This bug appear only for entities without inheritance.
I think this bug is due to the
LIMIT 1clause happening onfindOneBywhich also applies on joins generated here.For instance, the generated SQL statement generated might look like
@doctrinebot commented on GitHub (Oct 10, 2014):
@doctrinebot commented on GitHub (Jan 22, 2015):
Comment created by scaytrase:
Still expiriencing it at 2.5.0-alpha (
b889e18a9a). findOneBy cuts many-to-many association with fetch eager by 'LIMIT 1'@doctrinebot commented on GitHub (Jan 22, 2015):
Comment created by @ocramius:
[~scaytrase] yeah, we don't have a fix for it yet: I suggest providing a PR with the failing test first, and if we can't get to it, trying to patch it yourself, or at least find out which code bit affects this behavior.
@doctrinebot commented on GitHub (Jan 22, 2015):
Comment created by scaytrase:
I'm finishing such PR now. Will supply it to github soon
@doctrinebot commented on GitHub (Jan 22, 2015):
Comment created by scaytrase:
here it is
https://github.com/doctrine/doctrine2/pull/1277
http://www.doctrine-project.org/jira/browse/DDC-3531
Here is the failed travis build
https://travis-ci.org/scaytrase/doctrine2/jobs/47921568
@doctrinebot commented on GitHub (Jan 23, 2015):
Comment created by @doctrinebot:
A related Github Pull-Request [GH-1277] was assigned:
https://github.com/doctrine/doctrine2/pull/1277
@doctrinebot commented on GitHub (Jan 23, 2015):
Comment created by @doctrinebot:
A related Github Pull-Request [GH-1277] was closed:
https://github.com/doctrine/doctrine2/pull/1277
@doctrinebot commented on GitHub (Jan 24, 2015):
Comment created by @doctrinebot:
A related Github Pull-Request [GH-1280] was labeled:
https://github.com/doctrine/doctrine2/pull/1280
@doctrinebot commented on GitHub (Jan 24, 2015):
Comment created by @doctrinebot:
A related Github Pull-Request [GH-1277] was labeled:
https://github.com/doctrine/doctrine2/pull/1277
@doctrinebot commented on GitHub (Jan 24, 2015):
Comment created by @doctrinebot:
A related Github Pull-Request [GH-1280] was assigned:
https://github.com/doctrine/doctrine2/pull/1280
@doctrinebot commented on GitHub (Jan 25, 2015):
Comment created by @doctrinebot:
A related Github Pull-Request [GH-1280] was merged:
https://github.com/doctrine/doctrine2/pull/1280
@doctrinebot commented on GitHub (Jan 25, 2015):
Comment created by @ocramius:
Handled in DDC-3534
@doctrinebot commented on GitHub (Jan 25, 2015):
Issue was closed with resolution "Fixed"
@doctrinebot commented on GitHub (Jan 28, 2015):
Comment created by mbeccati:
FYI the test is failing on: https://revive.beccati.com/bamboo/browse/PHP-DOCTR-PHP54-249/test/case/18357533
As far as I can tell from https://www.sqlite.org/lang_select.html SQLite doesn't support OFFSET w/o LIMIT.
@doctrinebot commented on GitHub (Jan 28, 2015):
Comment created by @deeky666:
[~mbeccati] I believe this is fixed already by https://github.com/doctrine/dbal/pull/782
@doctrinebot commented on GitHub (Jan 28, 2015):
Comment created by mbeccati:
My mistake. The build wasn't cleaning up the vendor dir before running composer update, so it was still using an old dbal.