After inspecting some cache entries in the civicrm_cache table I've come across the field called 'expired_date' which is set to NULL in all cases.

The only reference to the field I can find anywhere in the codebase is in the schema file. So it looks like this is an old field definition that is no longer used and can be removed?


I had the same reaction when I saw that field -- it doesn't appear to be used.

In fact, I don't think it was ever used. Grepping some of the older releases (http://svn.civicrm.org/civicrm/branches/v2.0, http://svn.civicrm.org/civicrm/branches/v2.2), the field appears as part of the 2.1 schema upgrade; however, even then it's not used in any logic.

My suspicion is that the field is more aspirational. (Theory: One person designed the cache layer and included expired_date in the schema because it's standard in caching systems; then another person implemented the cache logic but ignored that part of the design.)

I wish the cache supported expiration/TTL, so I'm not anxious to remove the field. It would be even better if someone finished TTL support.

| improve this answer | |
  • OK, I shalln't create an issue to remove it. I wouldn't want to hurt CiviCRM's feelings by removing its aspirations ;] – John Jun 17 '15 at 21:31
  • I think we should make CiviCRM meet its aspirations! – ErichBSchulz Dec 27 '16 at 22:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.