Question about using Memcache API module

Events happening in the community are now at Drupal community events on www.drupal.org.
dparkmit's picture

Hi All,

I have a question on how to set up the Memcache API module on my Drupal 6 site for the first time.

The Memcache API documentation states that "In addition, if you have modules that implement their own cache tables using the cache API, they need to also implement the hook_devel_caches hook."

I have at least a couple of contrib modules such as Views that use their own cache tables. The code for the Views module doesn't contain an implementation of the hook_devel_caches hook. But when I checked out the cached keys in my memcached sever, I found Views-related keys.

Does the fact that the memcached server has Views-related keys mean that I don't have to actually write a views_hook_devel_caches function? Or do I need to write one anyways?

Also, if I write a views_hook_devel function, then can I just put that in a separate module that I write (e.g., Views Memcache) or do I need to add the views_hook_devel function to the Views module itself?

Thanks for the help!

David

Comments

The code for the Views module

Garrett Albright's picture

The code for the Views module doesn't contain an implementation of the hook_devel_caches hook. But when I checked out the cached keys in my memcached sever, I found Views-related keys.

I'm not familiar with the Memcache API module, but is it possible that it has the hook implementation? I would say it's likely.

Also, if I write a views_hook_devel function, then can I just put that in a separate module that I write (e.g., Views Memcache) or do I need to add the views_hook_devel function to the Views module itself?

Never hack other modules if you can help it - it's best to do it in your own module.

hook_devel_caches() was

Jonah Ellison's picture

hook_devel_caches() was deprecated and is not used in Drupal 6.

See http://drupal.org/node/339056

High performance

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: