-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
[10.x] Clean up DBAL deprecations #45289
Conversation
class NoPendingMigrations | ||
use Illuminate\Contracts\Database\Events\MigrationEvent as MigrationEventContract; | ||
|
||
class NoPendingMigrations implements MigrationEventContract |
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.
For some reason this event didn't have the MigrationEvent
contract which seemed odd to me. I can't think of a reason why it shouldn't have this.
d369ee6
to
23fda3c
Compare
@@ -164,7 +164,7 @@ public function testChangingColumnWithCollationWorks() | |||
[ | |||
'CREATE TEMPORARY TABLE __temp__users AS SELECT age FROM users', | |||
'DROP TABLE users', | |||
'CREATE TABLE users (age INTEGER NOT NULL COLLATE "NOCASE")', | |||
'CREATE TABLE users (age INTEGER NOT NULL)', |
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.
I guess these now will take the default collation.
'DROP TABLE users', | ||
'CREATE TABLE users (name VARCHAR(255) DEFAULT NULL COLLATE "BINARY")', | ||
'INSERT INTO users (name) SELECT name FROM __temp__users', | ||
'DROP TABLE __temp__users', |
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.
It seems DBAL is now smarter here and doesn't creates temporary tables anymore when only a unique constraint or an index is added to the table.
23fda3c
to
fff37a0
Compare
This PR fixes some deprecations from the move to Doctrine DBAL v3 (since we're dropping support for DBAL v2). Most likely these will be removed in Doctrine v4. There's still a couple of left which I haven't determined the right path to migrate to yet. Left some notes on other quirks I found below.