[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:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.9
Component:  Cache API                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note                                           |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests needs-
     dev-note
 * version:  6.1 =>


Comment:

 This will need a dev note:

 - alerting devs checking/setting the query caches directly
 - advice on how to use them in older versions of WP (ie, copy-pasta
 wrapped in a `function_exists()`
 - noting the cache invalidation upon upgrade due to the cache key changes

 I'm sure we'll think of more in the time between now and 6.9.

 I've unset the version, as they apply to bugs rather than enhancements.

 @spacedmonkey Enormous props for your work on this, thanks for your
 patience as architecture and naming was worked out.

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