Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The feature here is a configurable option to set a cache item in Drupal's cache table when a user (or anon/IP address) has voted on a particular piece of content. The advantage to checking for this cache item over the using VotingAPI's functions/tables is that many high performance sites store Drupal's cache table in a faster store, such a Memcached. So, for these systems, this cache item could improve performance by replacing checks in the DB with those in the faster cache.
There are also a few trivial cleanups in this patch that are unrelated to the main functionality.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | dec-cache.patch | 6.97 KB | ezra-g |
| decisions-alt-cache.patch | 4.8 KB | ezra-g |
Comments
Comment #1
ezra-g commentedHere's a more elegant way of doing this: Check for this cache item by default, and under the default configuration, check the VotingAPI for a vote as a fallback. That way, high performance sites can disable the fallback. Also, this patch implements a dedicated cache for these items, so that this cache can be selectively preserved.
I plan to commit this shortly.
Comment #2
ezra-g commentedThis is now committed. Remember to run update.php ;).
Comment #3
anarcat commentedHave you looked at #48394: cache voting results? I am not sure those two are related, but we have long required IVR results to be cached since sometimes winners need to be chosen at random in some very specific cases, and results therefore *need* to be cached to be exact... At least that's the way it was settled in advpoll, and I feel we are lacking here..