You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Potentional fix could be changing the migration to:
publicfunctionup()
{
/** * SQLite will only allow one per transaction when modifying columns. */Schema::table($this->prefix.'channelables', function (Blueprint$table) {
$table->renameColumn('published_at', 'starts_at')->nullable()->change();
$table->index('starts_at');
});
Schema::table($this->prefix.'channelables', function (Blueprint$table) {
$table->dateTime('ends_at')->after('starts_at')->nullable()->index();
});
}
Strange one, I've not come against this and we do have a test case which should run migrations and then rollback to ensure this kind of thing works. If you think this is a fix then happy to see a PR and we can take a look :)
Expected Behaviour:
Running all migrations without errors.
Actual Behaviour:
I get an error when running migrations on the following table:
2022_01_18_100000_add_starts_ends_at_to_channelables_table
error:
Steps To Reproduce:
composer require lunarphp/lunar:"^1.0.0-alpha" -W
php artisan migrate
The text was updated successfully, but these errors were encountered: