Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Since we move the config into the db and stopped using CachedStorage we only use cache.config for storing a key will all the schema. This seems wasteful.
Plus it gets in the way of refactoring CachedStorage to support collections see #2262861: Add concept of collections to config storages
Making a major and not a beta blocker since it makes the patch on #2262861: Add concept of collections to config storages smaller and easier to understand.
Comment | File | Size | Author |
---|---|---|---|
#2 | 2263255.2.patch | 2.39 KB | alexpott |
cache-config-removal.patch | 2.38 KB | alexpott | |
Comments
Comment #1
Berdircache schema is basically a plugin cache, those all switched to cache.discovery, feels a bit weird but should we do that too?
We won't need this on normal page requests, so there's no need to put it into APC/FileStorage like the others, but it might be more consistent?
Comment #2
alexpottMakes sense to me.
Comment #3
BerdirLooks good. Not mentioned here, but the new collection-supporting cached storage will use cache bins dynamically, so we won't need the hardcoded definition anymore.
Comment #4
webchickCommitted and pushed to 8.x. Thanks!