-
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
Merge 2.18.x up into 3.0.x #11202
Merge 2.18.x up into 3.0.x #11202
Conversation
It is strictly beneficial for the Psalm baseline.
Use a more specific type for getSqlStatements()
This will help to make sure we don't lose those parts of the SQL when working on doctrine#11188.
…utput-walker-test Cover limit/offset values in `LimitSubqueryOutputWalkerTest`
Fix calls to removed lock methods (doctrine#11061)
Merge 2.17.x up into 2.18.x
Conflicts: phpstan-dbal2.neon phpstan-persistence2.neon phpstan.neon psalm-baseline.xml psalm.xml src/Persisters/Entity/BasicEntityPersister.php src/Query/Exec/MultiTableUpdateExecutor.php src/Utility/LockSqlHelper.php tests/Tests/ORM/Functional/Locking/LockTest.php tests/Tests/ORM/Tools/Pagination/LimitSubqueryOutputWalkerTest.php
1696d53
to
da6c6f7
Compare
Strange, tests run on my machine both with SQLite and MySQL as the primary configured drivers |
Try downgrading to DBAL 3 ;) |
So the reasons really is certain platforms generating different SQL in DBAL 3 vs 4? How could I best write a portable test? |
I think asserting SQL in the ORM is wrong. The best test for this should be a functional one. For now, I suggest you skip this test when DBAL 3 is in use, and create an issue about rewriting such tests. |
@greg0ire I think I found a way to make the tests work for both DBAL 3 and 4. |
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.
Nicely done. I think it still looks weird and we still should rewrite this test, but definitely not in this PR 👍
LimitSubqueryOutputWalkerTest