I created several migrations that are related to each other, having foreign keys and etc ... but I do not want to mix them with migrations related to auth, permissions and etc.
My question is: Can I create a subfolder to organize my migrations within database / migrations?
Since this requires a little more command line to run the migration of a specific folder, I wanted to know if this is bad practice and etc, because another friend of mine said that this is not correct.
I believe not to be necessary, effort does not compensate for the return in this organization, other than controllers, models, and views, which are groups of code logic to which you constantly return to work, and therefore the larger and more complex your system , more file organization hierarchies can bring productivity, with each migration you work only once and perform your function in changing the bank.
They should not be "reused", including running the rollback, if necessary, will be on a single occasion of unsuccessful improvement deployment.
