[4.x] Support database
cache store tenancy
#1290
Draft
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.
This PR adds the DatabaseCacheBootstrapper. The bootstrapper can be used instead of CacheTenancyBootstrapper for the tenant cache to be saved in the tenant databases instead of keeping it in the central DB.
On
bootstrap()
, DatabaseCacheBootstrapper sets thedatabase
cache store's connection to 'tenant' and deletes thedatabase
cache store from the CacheManager's resolved stores -- this forces the manager to resolve a new instance of thedatabase
store created with the 'tenant' DB connection on the next cache operation.On
revert()
, the bootstrapper reverts thedatabase
cache store's connection back to the originally used connection (again, by altering the database cache store's configured connection and deleting thedatabaes
store from the manager's resolved stores).Solves #852