eZ Publish can create a lot cache.

When modifications on a class are stored, all cache are cleared.

This can sometimes lead to failure and it can produce some strange problems.

For example, i add last week the following effect on a class that had 7 attributes. The class modification failed because there were too many cache to expire. Every object of that class had only 2 attributes in database where as the class has 7.

Storing contentclass modifications should be separated from expiring cache.