[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 peterwilsoncc):

 @spacedmonkey Yes, I saw that. I'm just wondering whether it would be
 better to write the code once rather than duplicating it for each instance
 of a cache key using lastchanged. If it were once or two locations, I'd be
 happy to copy-paste but with 18ish occurrences in core it seems better to
 me to unify the code in a single location.

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