In Laravel 9, altering a column from unique(true) to unique(false) while the column is nullable preserves the nullable status. However, in Laravel 11, changing a column from unique(true) to unique(false) automatically alters the column to not null.
Why does changing a column's uniqueness from unique(true) to unique(false) in Laravel 11 automatically make it not null, while in Laravel 9, it preserves the nullable status of the column ?
#Difference Between unique() in Laravel 9 and Laravel 11 migrations
lost kettle
lost kettle
Difference Between unique() in Laravel 9 and Laravel 11 migrations
thorn oxide
Are you sure it's not due to this breaking change; https://laravel.com/docs/11.x/upgrade#modifying-columns? You'd need to add all the modifiers when performing a change now
lost kettle
I 've reviewed it and realized I missed that. I'd like to understand the reason for this. Was there any security issue or any github's issue which has further information about this topic?