Refresh connection resolver for models after switching database and fix cache prefixes not being updated #355
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.
Refresh connection resolver for models after switching database
Model::$resolvercontains adbinstance with a database name. After switching to a different database, thedbinstance in theModel::$resolvershould also be updated to the newly configureddbinstance. This fixes route model binding on Laravel Octane.Fix cache prefixes not being updated
Simply calling
Cache::forgetDriver()isn't enough to update cache prefixes everywhere. TheCacheManageralso keeps a copy of the old config incacheand theCachefacade itself keeps an old copy of theCacheManager. All of these should be cleared and forgotten after switching cache configs.