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.

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

[#56] Db rollback uses second latest migration #57

Merged

Conversation

rpbaltazar
Copy link
Contributor

@rpbaltazar rpbaltazar commented Jun 1, 2020

If we have a default schema set as part of the list of the tenants, the tasks will run twice for the default schema. once for the default rails behavior and the other by iterating over all tenants.
This ensures that if the default schema is part of the tenant_list it is excluded when running the tasks

@rpbaltazar rpbaltazar linked an issue Jun 1, 2020 that may be closed by this pull request
@rpbaltazar rpbaltazar merged commit 443bebf into development Jun 1, 2020
@rpbaltazar rpbaltazar deleted the db-rollback-uses-second-latest-migration-56 branch June 1, 2020 11:32
@rpbaltazar rpbaltazar mentioned this pull request Jun 1, 2020
rpbaltazar added a commit that referenced this pull request Jun 2, 2020
Prepare Release - 2.6.1

# Enhancements

- N/a

# Bugfixes

- [Resolves influitive#607] Avoid early connection
  - #39
  - #53
  - #51
- [Resolves #52] Rake db:setup tries to seed non existent tenant - #54
- [Resolves #56] DB rollback uses second last migration - #57

# Chores

- N/a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

db:rollback uses second latest migration for tenants
1 participant