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
Hi there!
First of all; great work! Just used it in a simple project to keep my database updates maintained via migrations and it worked instantly!
Maybe it's good to add PDO transaction while executing migrations. Since an error can be thrown during the update, it's useful to rollback() the changes so the migration can be fixed and re-applied (mostly while developing the migration).
This could also be a setting, to enable transaction. But basically it should be the default.
The text was updated successfully, but these errors were encountered:
Keep in mind this project is not maintained for more than 3 years. Nowadays I'm not working with PHP anymore, provided that, feel free to send a PR.
I believe we just need to open the transaction in the files MigrationExecuteCommand.php and MigrationMigrateCommand.php but I'm not sure
Yeah I already tried to achieve it.
Didn't notice the inactivity :-) it still works great.
I currently use it for a demo project, but I can believe it could be useful for non-framework projects.
Hi there!
First of all; great work! Just used it in a simple project to keep my database updates maintained via migrations and it worked instantly!
Maybe it's good to add PDO transaction while executing migrations. Since an error can be thrown during the update, it's useful to rollback() the changes so the migration can be fixed and re-applied (mostly while developing the migration).
This could also be a setting, to enable transaction. But basically it should be the default.
The text was updated successfully, but these errors were encountered: