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

 Replying to [comment:18 rmccue]:
 > I think I had originally suggested this when chatting with @spacedmonkey
 (although, I'm not the CTO :D),

 Sorry for getting your job title wrong.

 >
 > Most of WP is designed ''not'' to use key-based invalidation generally,
 so this was a pretty big conceptual change to the design of the cache
 system as a whole; moving back to regular keying I think makes the most
 sense and keeps it consistent. I can see a case for key-based
 invalidation, but WP was never really designed for that, so switching it
 has caused some issues.

 Sorry, are your for or against this change. I find this message unclear.

 BTW, I understand this is a big change, which is why I want the feedback
 from the community.

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