-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: spark migrate
-g
option
#7894
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need a changelog note?
Rollback specifies a batch number and returns the database to that state. It is not possible to specify a specific group to return to a state.
ed9ba07
to
a58258f
Compare
@MGatner Rebased and added changelog. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks good.
Hello everyone, I have had the same recent problem with version 4.4.1 having the CI_ENVIRONMENT in "development", review the code of the file \system\Database\MigrationRunner.php and comment the following lines (849 - 855):
this solved my problem. It should be allowed that regardless of whether your CI_ENVIRONMENT is "production", "testing" or "development" you can rollback without any problem. |
Hello, I found a better way to solve and modify these two files: In \system\Commands\Database\MigrateRollback.php lines 84-86 and 93:
In \system\Database\MigrationRunner.php lines 236-240:
|
Your customization is yours, no problem. But the specifications of the CI4 migration are:
If you find any behavior against the spec, feel free to create an issue or send a PR. |
Description
See #7891
-g
inspark migrate
,migrate:refresh
, andmigrate:status
-g
option inspark migrate:rollback
because it does not work (and should not work)The current behavior
migrage:rollback
:migrate:status
:Checklist: