0
I’m starting to use that framework and I realized that the migrations when not created in a time cycle for execution there can be several errors, this is normal?
For example if you create a migration city but she has a constraint with a migration of a natural person migration was created after the city or is in the execution of the command php artisan migrate a problem will occur because the second migration will not be active yet, this cycle I realized would be correct?
If you’re right about that framework is very based on design patterns ie whether you should think very carefully before doing things, or has ways to reverse the process of creating migrations, example have a migration and then I want to reverse her execution to before another?
I don’t know much about Laravel, but from what he said the logic is that one thing is tied to another, similar to the foreign key, so basically the answer is yes, you need to design before you start "creating"Of course, you can do both at the same time, but you have to have a sense of how to design. Soon someone who understands Laravel appears to answer with more details :)
– Guilherme Nascimento
I think Laravel Migrations had to be equal to cakephp: You can run a specific.
– Wallace Maxters