Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Dumps with multi-db configurations are not updated after execution rake db:migrate for single DB #38976

Closed
alvir opened this issue Apr 17, 2020 · 5 comments
Closed

Dumps with multi-db configurations are not updated after execution rake db:migrate for single DB #38976

alvir opened this issue Apr 17, 2020 · 5 comments

Comments

@alvir
Copy link
Contributor

alvir commented Apr 17, 2020 •
edited

I've checked this in code and I've noticed that we don't create any dumps.

Steps to reproduce

  1. We have to DBs primary and secondary
  2. Execute rake db:migrate:secondary first time

Expected behavior

The file secondary_schema.rb exists and actual

Actual behavior

The file secondary_schema.rb is absent.

System configuration

Rails version: 6.0.2.2

Ruby version: 2.7.1
@alvir
Copy link
Contributor Author

alvir commented Apr 17, 2020

@eileencodes

Probably you know everything about it

@alvir
Copy link
Contributor Author

alvir commented Apr 17, 2020

I haven't found a quick fix for it.

@eileencodes
Copy link
Member

eileencodes commented Apr 17, 2020 •
edited

Thanks for the report! This was fixed in #38449

@alvir
Copy link
Contributor Author

alvir commented Apr 17, 2020

Thanks a lot. I skipped these changes in this PR

@alvir
Copy link
Contributor Author

alvir commented Apr 17, 2020

@eileencodes I found fix in #38586. I had to check master. Sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alvir @eileencodes