![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
#63195 closed defect (bug) (duplicate)
Unify timestamps of query cache keys
| Reported by: | tillkruess | Owned by: | flixos90 |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.9 |
| Component: | Cache API | Version: | |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: | performance |
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.
16 months ago
#1
- Keywords has-patch added
#4
@
15 months ago
- Focuses performance added
- Milestone Awaiting Review → 6.9
- Owner set to
- Status new → reviewing
@tillkruess commented on PR #8616:
13 months ago
#5
Closing in favor of #8728.
This ticket was mentioned in Slack in #core by westonruter. View the logs.
9 months 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