I've found an edge case where I need to specify which cache bin to add the query results into. My case involves a large result set where I'm using memcache and the item to be cached is over the slab size allowed by memcache. In this instance, it silently fails.

What I'd like to do here is to be able to tell memcache "don't keep cache_my_bin_name in memory, send it through to the database" but the current version of this module assumes I'm always using the default 'cache' table/bin.

The patch I've written allows developers to provide an override in the cache options which can, on its own, be used to specify which table to put data in... or in the case of other caching solutions allow a bit more flexibility in where query results are stored.

Hope this is of use to others too.

Members fund testing for the Drupal project. Drupal Association Learn more


johan.gant’s picture

Plazik’s picture

Title: Allow override of which cache bin GAFeed.lib.inc uses » Allow override of which cache bin google_analytics_reports_api.lib.inc uses
Version: 6.x-1.3 » 7.x-3.x-dev
Issue summary: View changes
1.37 KB

johan.gant, thank you for the patch. I've re-rolled it for the latest 7.x-3.x verison.

  • Plazik committed 9da5a70 on 7.x-3.x authored by johan.gant
    Issue #1930180 by johan.gant, Plazik: Allow override of which cache bin...
Plazik’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.