Issue Feature Rejected

#20500Change the DB backend to use a default cache table

Ingo Renner 05/25/09, 13:37 updated 06/01/13, 14:45

Description

currently you have to set up a separate table for each cache using the DB backend. To ease the use of the DB backend by default everything should go into a default table. A separate table can then still be defined for performance reasons f.e.

(issue imported from #M11181)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.