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
Im sorry if i can't get a better description for the title, but i will try to explain this the best i can:
When a child entity has another child, and this last one has a child that is the parent of the first one, workbench begins to consume memory incrementally, just like a recursion problem (at least to me), but here is the thing:
first, i'm going to describe the models by following laravel's conventions:
Role:
has many users
belongs to many access rules
belongs to one institution
User:
has many institutions
belongs to one role
Institution:
has many roles
belongs to one user
Here a screenshot for reference:
Everything goes fine If i remove this FK:
or this one:
or this one:
But if i keep all this relations, the problem occurs when i click on "Tools->Catalog->Export Laravel 5 Migration" menu.
My env:
OS: MacOS High Sierra
Macbook Pro Retina 15 mid 2015
Workbench: 8.0.15 (same results in version 6)
Plugin version: current Master Branch (0.1.15)
Im sorry if i can't get a better description for the title, but i will try to explain this the best i can:
When a child entity has another child, and this last one has a child that is the parent of the first one, workbench begins to consume memory incrementally, just like a recursion problem (at least to me), but here is the thing:
first, i'm going to describe the models by following laravel's conventions:
Here a screenshot for reference:
Everything goes fine If i remove this FK:
or this one:
or this one:
But if i keep all this relations, the problem occurs when i click on "Tools->Catalog->Export Laravel 5 Migration" menu.
My env:
OS: MacOS High Sierra
Macbook Pro Retina 15 mid 2015
Workbench: 8.0.15 (same results in version 6)
Plugin version: current Master Branch (0.1.15)
Ref. Workbench file for testing:
recursive_relations_err.mwb.zip
The text was updated successfully, but these errors were encountered: