Error during "Export Laravel 5 Migration" #18
Comments
|
Would you be able to share your model to help diagnose this? |
|
Same error on windows too +1 |
|
@ahmedfathi1 Which version do you have? Latest from master? |
|
You can see here, its is the latest from master. |
|
plz lemme know if you need more info. |
|
@RizwanAslam I tested it, can you please post a log? Please show us the log, Help > Show Log File |
|
I tested in on latest version of Workbench 6.3 CE on Windows and it works. Just post log files. |
|
I'm using version latest from master... and Workbench V.6.3 on linux (ubuntu 16.04) I tested it on different databases My log file :
|
|
@ahmedfathi1 It appears that the error is caused by a missing index.name on a foreign key, though I'm unsure why as of now. Please pull the latest from master and let us know if it works now. |
|
@beckenrode Excellent... It's working now |
|
hi, im having the same issue, im using Mac OS X 10.11.6, MySQL Workbench Community (GPL) for Mac OS X version 6.3.6 CE build 511 (32 bit)
|
- Added testing Model - Fix for beckenrode#18 - Fixed issues with 'CURRENT_TIMESTAMP', 'NULL ON UPDATE CURRENT_TIMESTAMP', 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP' - Check for non existing column types - Fixed index keys, primary key is no longer included - Added .gitignore
- Added testing Model - Fix for beckenrode#18 - Fixed issues with 'CURRENT_TIMESTAMP', 'NULL ON UPDATE CURRENT_TIMESTAMP', 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP' - Check for non existing column types - Fixed index keys, primary key is no longer included - Added .gitignore
|
@gin1314 You can test this fork https://github.com/VeeeneX/mysql-workbench-export-laravel-5-migrations, until it gets merged. |
|
@VeeeneX thanks! 👍 , will give it a try |
* Updates - Added testing Model - Fix for #18 - Fixed issues with 'CURRENT_TIMESTAMP', 'NULL ON UPDATE CURRENT_TIMESTAMP', 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP' - Check for non existing column types - Fixed index keys, primary key is no longer included - Added .gitignore
|
Fixes are in master branch, should be fixed now |
|
I received the same error, workbench 6.3 (6.3.4.9 build828 64bits), ubuntu 15.10 |
|
@IgorDePaula Thanks for pointing out this issue, is it possible to show your model or give some kind of example of model so we can prevent this bug in future I will create a hot fix for this :) |
|
|
|
@VeeeneX Sorry for late reply. 13:55:20 [INF][ SqlEditor]: Opened connection 'Local instance wampmysqld64' to MySQL Community Server (GPL) version 5.7.11 |
|
Xampp on mac, model with foreign keys, workbench freezes unfortunatelly. MySQL Workbench Community (GPL) for Mac OS X version 6.3.6 CE build 511 (32 bit). |
|
@IgorDePaula Please try the latest from master to see if it solves this problem. |
|
Tried with latest from master. unfortunately still hangs. |
|
@arysom could you share your log file and/or your model so that this can be further looked into? |
|
I'm using it normally. |
|
I just got a very similar issue to this, by stripping back my tables i realised that i had one on my model that was not on my EER diagram that wasn't properly set up. i.e i hadn't selected the column types, so i was getting this error in my log: |
|
also be aware of FULLTEXT indexes: they also can't be proceeded |
|
@veganista It's hard to tell where the issue is can you post your model? |
* Updates - Added testing Model - Fix for #18 - Fixed issues with 'CURRENT_TIMESTAMP', 'NULL ON UPDATE CURRENT_TIMESTAMP', 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP' - Check for non existing column types - Fixed index keys, primary key is no longer included - Added .gitignore * Updates - Added testing Model - Fix for #18 - Fixed issues with 'CURRENT_TIMESTAMP', 'NULL ON UPDATE CURRENT_TIMESTAMP', 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP' - Check for non existing column types - Fixed index keys, primary key is no longer included - Added .gitignore * Fix for #30 And possible for padding as well as small fixes
|
I am also getting the same issue. I know my model is messed up but still having a log will help us to identify the failing table and column. line 391, in export_schema i tried to add logs myself but of curse i know nothing about phyton :( |
|
@beckenrode I tried the plugin today again, continue fails... =/ |
|
I received this message: |
|
@beckenrode I can confirm that the issue is caused by having a fulltext index in the model. Removing it does the trick and migration get's generated. On a side note, are there any plans to include the triggers and associated scripts into the export? |
|
Hi I'm having a similar issue when trying to run the plugin.
Workbench Version: 8.0.14 Here's my model: And the log file entries: |
did you find any solution? |
|
In case others have an issue - I also ran into the same error @namelus and others reported. TLDR;
|
I installed this plugin as described in documentation file .
I tried to export my database using
but it's showing error
error calling Python module function GenerateLaravel5Migration.generate_laravel5_migrationThe text was updated successfully, but these errors were encountered: