Overview
| Comment: | A hash prefix lookup is always an indexed range, so a branch name no longer scans every check-in |
|---|---|
| Timelines: | family | ancestors | descendants | both | prefix-range |
| Files: | files | file ages | folders |
| SHA3-256: |
2b3185cadeca0cd0283091bcbb9c32c0 |
| User & Date: | dmestas on 2026-10-30 21:55:25.161 |
| Other Links: | branch diff | manifest | tags |
Context
|
2026-10-30
| ||
| 23:06 | land prefix-range check-in: f226141a29 user: dmestas tags: trunk | |
| 22:07 | A rendered body answers its full hashes in a few batched queries, and local ticket redirects seek an index closed check-in: 8dd54e9fb7 user: dmestas tags: hash-batch | |
| 21:55 | A hash prefix lookup is always an indexed range, so a branch name no longer scans every check-in closed check-in: 2b3185cade user: dmestas tags: prefix-range | |
| 21:50 | land hash-lookups check-in: 11601acc88 user: dmestas tags: trunk | |
Changes
Modified internal/index/index.go
from [85fb2ea899]
to [74866e43d5].
[diff]