Hey,
The same issue is also with me.
I am working with dynamic databases.
I've created run time databases as per the requirements.
and every time i work with this i need to create a new database even to test .
With the new database migration works well as Godlike.
but if we want to execute the migration for the old databases it shows me everything OK in the console.
and There is one more thing which I have observed each time when i am executing the migration, the migrations table is getting redundant data for the migrations executed every time.
I'd like to suggest the team that we can create a batch like migration system.
that every time it getting executed so there can be a file which can be possibly fast and feasible way to get all the migrations executes as per the requirements.
You guys are doing a great job. Please let me know if I can help.
Hey,
The same issue is also with me.
I am working with dynamic databases.
I've created run time databases as per the requirements.
and every time i work with this i need to create a new database even to test .
With the new database migration works well as Godlike.
but if we want to execute the migration for the old databases it shows me everything OK in the console.
and There is one more thing which I have observed each time when i am executing the migration, the migrations table is getting redundant data for the migrations executed every time.
I'd like to suggest the team that we can create a batch like migration system.
that every time it getting executed so there can be a file which can be possibly fast and feasible way to get all the migrations executes as per the requirements.
You guys are doing a great job. Please let me know if I can help.