PoolConfig
no longer keeps a reference to the connection class (attempt 3)
#54366
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation / Background
Alt to #54350 and #54349, fixes #54343
Detail
This is variation on #54349 that extends
ConnectionHandler::StringConnectionName
to trackprimary_class?
, and introducesActiveRecord::Base.preventing_writes?
that will accept a connection name and do the same thing thatcurrent_preventing_writes
does on a record class.Checklist
Before submitting the PR make sure the following are checked:
[Fix #issue-number]