Open riyuatarashi opened 1 month ago
This tends to happen if you have a problem with the migration and try to rerun it. Due to how databases work, actions like alter table
can't be rolled back with transactions. In this case, the problem is likely as follows:
Because of this limitation, always run migration with a clean state.
In your case, have you tried upgrading to v7.0.2?
Describe the bug The migration forward 7.0 failed because of an already existing column name
position
on migrationdatabase/migrations/2024_01_27_171649_add_position_into_playlists_table.php
To reproduce Steps to reproduce the behavior:
Expected behavior Migration to pass.
Environment
7.0.2
8.1.2
Additional context laravel.log