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
Hi first +1 to this package. However there is some need that the worlds... migration runs before the other migration tables. For example I have users table that has country_id, city_id references world_countries ... Can this be added to the vendor publish? so that we can modify the naming? as I see the publish command only seeds.
PS- I am running artisan migrate:fresh --seed or artisan db:migrate for the first time. Let me know if this is something you would like I can raise a PR
The text was updated successfully, but these errors were encountered:
I see this was commented out here . I think a better way will be to rename the migrations to a date earlier than the default laravel users_table 2014_10_12_000000_create_users_table.php maybe to some older date 2013... what do you think @khsing ?
Hi first +1 to this package. However there is some need that the worlds... migration runs before the other migration tables. For example I have users table that has
country_id
,city_id
referencesworld_countries
... Can this be added to the vendor publish? so that we can modify the naming? as I see the publish command only seeds.PS- I am running
artisan migrate:fresh --seed
orartisan db:migrate
for the first time. Let me know if this is something you would like I can raise a PRThe text was updated successfully, but these errors were encountered: