Closed (duplicate)
Project:
Voting API
Version:
6.x-2.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Jul 2009 at 18:56 UTC
Updated:
12 Feb 2014 at 19:48 UTC
Jump to comment: Most recent
Comments
Comment #1
eaton commentedArguably, the table shouldn't be named _cache() at all, rather 'votingapi_results'. Unlike Drupal's core cache tables, it is NOT just a bin of keys with serialized data. It's an actual meaningful data schema and shouldn't be arbitrarily cleared the way Drupal's default cache tables can be.
Naming them the same way would probably cause more confusion, because they can't be treated the same way.
Comment #2
hefox commentedTurning this into a feature request
In #382866: provide script and documentation to rebuild the votingapi cache there's a way to rebuilt it, but not in the cache clear, so it's not really acting like a cache.
Also, having it end _cache instead of start cache_ does not clarify that due to other contrib modules using the _cache for their cache tables; ie. biblio_import_cache and views_object_cache.
Comment #3
drclaw commentedDuplicate of #1962178: Rename votingapi_cache into votingapi_results