[wp-trac] [WordPress Trac] #59592: Store last changed value in key instead of using it as a salt for query caches

[WordPress Trac]

#59592: Store last changed value in key instead of using it as a salt for query
caches
--------------------------------------+-----------------------------
 Reporter:  spacedmonkey              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Future Release
Component:  Cache API                 |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+-----------------------------

Comment (by tillkruess):

 Replying to [comment:22 peterwilsoncc]:

 > On the proposed implementation, I am wondeing if it would be better to
 introduce new `wp_cache` functions to do the checking of the last changed
 value as there are enough occurrences of the pattern in Core that it could
 be worthwhile (18, based on a quick check).

 A getter/setter function would be great, we'd just need to account for N
 timestamps, because some keys have multiple (posts+terms) for example.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/59592#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform