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

fix init after reload on development #53

Merged
merged 1 commit into from
May 25, 2020

Conversation

fsateler
Copy link
Contributor

@fsateler fsateler commented May 19, 2020

On 26fc746, init is not forced to be executed on to_prepare. This helps us avoid a connection at startup.
However, things break down after a reload because things like ExcludedModel.count don't go through
the connection method that we overrode, at least until after we queried the table name.

Let's make sure that we initialize before using arel too.

On 26fc746, init is not forced to be executed on `to_prepare`. This helps us avoid a connection at startup.
However, things break down after a reload because things like `ExcludedModel.count` don't go through
the `connection` method that we overrode, at least until after we
queried the table name.

Let's make sure that we initialize before using arel too.
@rpbaltazar rpbaltazar merged commit 3cfaeb4 into rails-on-services:development May 25, 2020
@fsateler fsateler deleted the bugfix/reload branch May 26, 2020 21:25
@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
@lunks lunks mentioned this pull request Oct 26, 2020
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.

2 participants