-
Notifications
You must be signed in to change notification settings - Fork 1
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
broken index migration in MariaDB #93
Comments
Thanks for reporting this. I'll try and fix this in the next few weeks, very happy to accept a PR sooner if you want to put one in! |
Here the confirmed - and still unresolved - bug in MariaDB. In my application I've just skipped the problematic migration, don't know if there is some alternative way to obtain a similar indexing behavior :-\ |
I just stumbled on this same bug, unfortunately in production... how can you skip a migration? |
@JanMisker in the file Ugly, and you will stay without proper indexes in DB, but yet the most quick and dirty solution for this. |
@madbob I ended up manually inserting an entry in the |
Describe the bug
Migrations (in particular: 2023_02_21_175500_add_indexes.php) fails when executed on MariaDB with the following error:
To Reproduce
Steps to reproduce the behavior:
composer require twigger/laravel-job-status
php artisan migrate
Additional context
Tested on MariaDB Ver 15.1 Distrib 10.6.12-MariaDB, for debian-linux-gnu (x86_64)
The text was updated successfully, but these errors were encountered: