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
rake db:migrate:redo executes db:structure:dump only once #5435
Comments
I can reproduce this issue. and I realize the cause of problem. |
kennyj
added a commit
to kennyj/rails
that referenced
this issue
Mar 17, 2012
I think that I fixed this issue. |
I confirmed that this issue is solved on 3-2-stable. |
tenderlove
added a commit
that referenced
this issue
Mar 18, 2012
Fix GH #5435. db:structure:dump should be re-enable.
kennyj
added a commit
to kennyj/rails
that referenced
this issue
Mar 18, 2012
drogus
added a commit
that referenced
this issue
Mar 18, 2012
[3-2-stable] Fix GH #5435. db:structure:dump should be re-enable.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In current branch 3-2-stable, when
config.active_record.schema_format = :sql
, the taskrake db:migrate:redo
dumps the database structure just after the first migration is rolled back, and never calls it again, so you are left with invalid structure file.Apparently the task
db:_dump
is reset properly, but the taskdb:structure:dump
is not, what may be seen in the last line of the trace:The text was updated successfully, but these errors were encountered: