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
On a fresh install of v4.0.0 in a fresh laravel project the migration fails.
Seems like both the "add_parameters_to_route_statistics_table" and "create_route_statistics_table" get created with exactly the same timestamp and thus the "add" one is run before the "create" one.
Your environment
Windows 10
Laravel v11.5.0
Laravel-route-statistics v4.0.0
Steps to reproduce
laravel new example-app
cd example-app
composer require bilfeldt/laravel-route-statistics
php artisan vendor:publish --provider="Bilfeldt\LaravelRouteStatistics\LaravelRouteStatisticsServiceProvider" --tag="migrations"
php artisan migrate
Expected behaviour
Migration should pass
Actual behaviour
PDOException::("SQLSTATE[42S02]: Base table or view not found: 1146 Table 'example_app.route_statistics' doesn't exist")
I could fix this on my end by giving new timestamps to the migration filenames and thus bring them in the correct order.
The text was updated successfully, but these errors were encountered:
Subject of the issue
On a fresh install of v4.0.0 in a fresh laravel project the migration fails.
Seems like both the "add_parameters_to_route_statistics_table" and "create_route_statistics_table" get created with exactly the same timestamp and thus the "add" one is run before the "create" one.
Your environment
Windows 10
Laravel v11.5.0
Laravel-route-statistics v4.0.0
Steps to reproduce
laravel new example-app
cd example-app
composer require bilfeldt/laravel-route-statistics
php artisan vendor:publish --provider="Bilfeldt\LaravelRouteStatistics\LaravelRouteStatisticsServiceProvider" --tag="migrations"
php artisan migrate
Expected behaviour
Migration should pass
Actual behaviour
PDOException::("SQLSTATE[42S02]: Base table or view not found: 1146 Table 'example_app.route_statistics' doesn't exist")
I could fix this on my end by giving new timestamps to the migration filenames and thus bring them in the correct order.
The text was updated successfully, but these errors were encountered: