Opened 4 weeks ago
Last modified 3 weeks ago
#63195 reviewing defect (bug)
Unify timestamps of query cache keys
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 6.9 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Cache API | Keywords: | has-patch |
Focuses: | performance | Cc: |
Description
This is a followup to #63194.
Currently the timestamp of query cache keys are un-parseable and they should be unified.
<hash>:0.91192600-1743003204:0.90454100-1743003204 <hash>:0.91192600-17430032040.90454100-1743003204 <hash>:0.90454100-1743003204
I propose this new format, where the primary cache group is always last:
<hash>:<2nd-group>+<group> <hash>:<group> <hash>:0.91192600-1743003204+0.90454100-1743003204 <hash>:0.90454100-1743003204
Change History (4)
This ticket was mentioned in PR #8616 on WordPress/wordpress-develop by @tillkruess.
4 weeks ago
#1
- Keywords has-patch added
Note: See
TracTickets for help on using
tickets.
This is a followup to #8615. Currently query cache keys are un-parseable and they should be unified.
I propose this new format, where the primary cache group is always last:
Trac ticket: https://core.trac.wordpress.org/ticket/63195