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

Prepare Release 2.6.0 #48

Merged
merged 22 commits into from
May 14, 2020
Merged

Prepare Release 2.6.0 #48

merged 22 commits into from
May 14, 2020

Conversation

rpbaltazar
Copy link
Contributor

@rpbaltazar rpbaltazar commented May 11, 2020

rpbaltazar and others added 22 commits May 5, 2020 10:54
- Each adapter is responsible for resetting the tenant info based on the way they behave
- `switch` relies on the `connect_to_new` implementation of each of the adapters
- Added test coverage for raised issue
…tence before switching

This is configurable by setting: tenant_presence_check. It defaults to true
in order to maintain the original gem behavior. This is only checked when using one of the PostgreSQL adapters.
The original gem behavior, when running switch would look for the existence of the schema before switching. This adds an extra query on every context switch. While in the default simple scenarios this is a valid check, in high volume platforms this adds some unnecessary overhead which can be detected in some other ways on the application level.

Setting this configuration value to false will disable the schema presence check before trying to switch the context.

Apartment.configure do |config|
  tenant_presence_check = false
end
- updated custom console to include welcome message
@rpbaltazar rpbaltazar merged commit 06182ba into master May 14, 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