The table you reference in the last foreign key statement is 'car' but the table is 'cars'.
Does this help?
Last updated
1 year ago.
This issue hasn't even been fixed in 5.1. What can we do to have Tyler fix this in the next release?
As I see, this is not a laravel issue, this is a MySQL issue.
IMHO, is not a bug, its a detail of implementation: you cannot reference a FK to a yet-not-created table and table PK.
The way around that is simple: order your migrations to guarantee that all FK declarations references pre-created tables.
Last updated
8 years ago.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast