This repository has been archived by the owner on Jan 10, 2020. It is now read-only.
Fix data type issue causing foreignkey constraint #208
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Laravel 5.7 create_users_table migration file comes with BigIncrement for the user ID while the grafite starter pack is just increment for Create_user_meta_table hence users encounter foreign key constraint error during migrate --seed.
Illuminate\Database\QueryException : SQLSTATE[HY000]: Ge
neral error: 1215 Cannot add foreign key constraint (SQL: alter table
user_meta
add constraintuser_meta_user_id_foreign
foreign key (user_id
) referencesusers
(id
) on delete cascade)The latest version of Laravel 5.8 is just increment but Grafite/Starter does not work properly with it.