-
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
Support for DBAL 3's platform classes #8946
Conversation
use function get_class; | ||
use function sprintf; | ||
|
||
// DBAL 2 compatibility | ||
class_exists('Doctrine\DBAL\Platforms\MySqlPlatform'); |
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.
That's a tricky one. The class name was changed from MySqlPlatform
to MySQLPlatform
. Class names are case-insensitive in PHP, so just using the new name would theoretically work. However, on a case-sensitive filesystem, autoloading would fail if the case does not match. This is why I'm triggering the autoloader with old and new class name.
lib/Doctrine/ORM/Tools/Pagination/LimitSubqueryOutputWalker.php
Outdated
Show resolved
Hide resolved
e94153d
to
4ec8eda
Compare
4f1ec5c
to
24407e5
Compare
Signed-off-by: Alexander M. Turek <me@derrabus.de>
24407e5
to
fdbc6b6
Compare
PR is ready again. |
Thanks @derrabus ! |
In DBAL 3, various platform classes have been removed or renamed. Furthermore, DBAL 3.2 will deprecate the
AbstractPlatform::getName()
method.This PR makes the necessary adjustments in ORM.