I'm starting to use this framework and I noticed that migrations when not created in a running cycle for execution can be several errors, is this normal?
For example, if you create a migration city but it has a constraint with a migration of the person%, migration of person was created after the city% there will be a problem because the second php artisan migrate will not be active yet, would this cycle I realized be correct?
If it's right this migration is very much based on design patterns, ie whether you should think hard before doing things, or have ways to reverse the framework creation process, eg I have a migrations and then I want to reverse change its execution to before another?