-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DDC-3346] #1277 find one with eager loads is failing #1280
[DDC-3346] #1277 find one with eager loads is failing #1280
Conversation
Hello, thank you for creating this pull request. I have automatically opened an issue http://www.doctrine-project.org/jira/browse/DDC-3534 We use Jira to track the state of pull requests and the versions they got |
I'l try to see what can I do this weekend |
$this->assertCount(2, $authors[0]->articles); | ||
} | ||
|
||
public function testFindWithEagerFetchAndOffsetWillNotHydrateLimitedCollection() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test will fail due to a DBAL bug
This bug does not affect 2.4.x, as the eager loading does not work with |
…ly created `CachedPersisterContext`
…e newly created `CachedPersisterContext`
…y created `CachedPersisterContext`
…wly created `CachedPersisterContext`
…wly created `CachedPersisterContext`
…ime, depending on choices
…en limiting and fetch-joining to-many eager associations
…ET repository API (must not hydrate collections)
…Up/tearDown of model-related tables)
…sting more than 1 row
…ling (better to just use private props)
85c23e2
to
97ea6a7
Compare
…er-loads-is-failing [DDC-3346] #1277 find one with eager loads is failing
@Ocramius the limit = null & offset = 0 is creating a query with just OFFSET and that is raising an error on PHP 5.6.5 (bundled libsqlite was updated to 3.8.7.2). |
@lcobucci this should be already fixed here |
My mistake, sorry =) |
Ping @scaytrase
Note that this is a first revision and needs refactoring, so please consider helping out with that if you can.
Ping @guilhermeblanco: please check the
CachedPersisterContext
stuff: it's dirty as heck, but that's because the persister internal generated SQL caching is inconsistent as heck too.Resolution path for 2.4.x will be to throw an exception if there is an offset or a limit.