Feature #54651
closed
Caching Framework should allow to fetch multiple entries at once
0%
Description
Currently a backend can only provide get() for an identifier, a string. It might however be useful to fetch multiple entries in some go to speed up fetching, if that backend supports it.
If the backend has a maximum (for example sql-query-size with IN-statement) The backend-driver should to fetch elements in chunks.
Updated by
Updated by Christian Kuhn about 9 years ago
- Status changed from New to Rejected
Similar to to #54652, I also think this is not a really good idea. If a code needs to fetch tons of different entries from a cache backend and knows that it needs to fetch multiple entries, then it probably used a wrong strategy on set() and should have set() more data in one go.
A change like that may give some benefit on certain backends (eg. it would allow a combined OR clause in DB backend), but other backend would probably have a hard time to comply with such an interface change.
At the moment, I see no good real life use-case that would make us implement such a huge change that could not be done in the application code.
Please come up with real life use cases where this architectural change could systematically help the system to open this issue again.