Laravel MySQL DB migrations failing since version 2.10.0 #3789
Comments
|
As discussed in laravel/framework#30539 this is being handled in Laravel. |
|
Closing as duplicate of #3714 |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug Report
Laravel Database Migrations failing since dbal upgrade from 2.9.2 to 2.10.0:
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'CHARACTER SET utf8mb4 NOT NULL COLLATE
utf8mb4_unicode_ci' at line 1 (SQL: ALTER TABLE user_federations CHANGE id id BIGINT UNSIGNED AUTO_INCREMENT CHARACTER SET utf8mb4 NOT NULL COLLATE
utf8mb4_unicode_ci)Current behaviour
When you have a string field and change it to a bigInteger field strange character set errors are occurring.
How to reproduce
Create a Laravel db migration with an string column and make another migration with a change to that column where you change it to bigInteger.
The text was updated successfully, but these errors were encountered: