Content type and part definitions should be cached


It's quite common to access type or part definitions in order to get settings, etc. Whenever that happens, one or several database queries are issued. When the definition is accessed in order to optimize other queries, this is particularly counter-productive.
This information should be perfectly safe to cache. First access could actually be pretty aggressive and bring all definitions down in one query.


pszmyd wrote Dec 20, 2012 at 9:57 PM

+1. Indeed, that data is rarely changed so it's a perfect target for caching.

abhishekluv wrote Dec 28, 2012 at 4:18 PM

+1 Yes

sebastienros wrote Mar 5, 2013 at 8:38 PM

Cache id by name at least to benefit from first level caching.

sebastienros wrote Apr 23, 2013 at 11:57 PM

Fixed in changeset 9f83dd566926

sebastienros wrote Apr 27, 2013 at 5:31 PM

Actually I fixed the wrong bug

sfmskywalker wrote Mar 28, 2014 at 12:28 AM

Fixed in changeset aef123846210eb9626daf031c4fb921b4a65c174