#63195 closed defect (bug) (duplicate)
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 (7)
This ticket was mentioned in PR #8616 on WordPress/wordpress-develop by @tillkruess.
8 months ago
#1
- Keywords has-patch added
#4
@
7 months ago
- Focuses performance added
- Milestone changed from Awaiting Review to 6.9
- Owner set to flixos90
- Status changed from new to reviewing
@tillkruess commented on PR #8616:
5 months ago
#5
Closing in favor of #8728.
#6
@
2 months ago
- Resolution set to duplicate
- Status changed from reviewing to closed
Duplicate of #59592.
This ticket was mentioned in Slack in #core by westonruter. View the logs.
3 weeks ago
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