Error during "Export Laravel 5 Migration"
See original GitHub issueI installed this plugin as described in documentation file . I tried to export my database using
tools->catalog->export laravel 5 migration
but it’s showing error
error calling Python module function GenerateLaravel5Migration.generate_laravel5_migration
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:34 (5 by maintainers)
Top Results From Across the Web
mysql workbench does not start after ... - Stack Overflow
Just installed mysql-workbench-community-8.0.25-winx64.msi on windows 10. Works fine until I install 'export-laravel-5-migrations.py' ...
Read more >Laravel 5 - Migrations from existing database - Laracasts
I would like to know how can I proceed for creating migrations from an empty existing database with Laravel 5. With L4, I...
Read more >Migrations & Seeding - The PHP Framework For Web Artisans
Migrations are a type of version control for your database. They allow a team to modify the database schema and stay up to...
Read more >Models and Migrations | Laravel Package Development
Migrations live in the database/migrations folder in a Laravel application. In our package we mimic this file structure. Therefore, database migrations will not ......
Read more >Check for background migrations before upgrading | GitLab
For a no-downtime deployment · Check the status of the batched background migration from the error message, and make sure it is listed...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In case others have an issue - I also ran into the same error @namelus and others reported.
TLDR; Removing foreign keys with unmatched tables resolved the issue for me.
I discovered MySQL WB created foreign keys that didn’t have corresponding tables. When I created my tables, I used the dropper tool to select the columns to create the relationships. Initially they were non-identifying relationships, then I changed them to identifying relationships.
In troubleshooting this issue, I looked at the table properties in the Model tab and I saw one set of relationships that corresponded properly to tables and one set that didn’t have tables matched to them.
When I removed the unmatched relationships, the migration files were generated properly with the expected foreign keys.
@beckenrode Excellent… It’s working now Thank you so much …