Drupal Association members fund grants that make connections all over the world.
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.