Overview
| Comment: | In fts5, account for the possibility of negative docids when allocating a buffer to store the results of merging detail=none prefix lists. Fix for report 2026-08-04T08:49:27Z. |
|---|---|
| Downloads: | See separate download page |
| Timelines: | family | ancestors | descendants | path-to-release | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
a7f8c92f623e9cbe8a61266d949916ac |
| User & Date: | dan on 2026-08-04 11:04:17.130 |
| Other Links: | manifest | tags |
Context
|
2026-08-04
| ||
| 13:44 | Fix a single byte buffer overrun in the approximate_match extension. (check-in: 7f380be91b ... user: dan tags: trunk) | |
| 12:29 | In fts5, account for the possibility of negative docids when allocating a buffer to store the results of merging detail=none prefix lists. (check-in: f8c72d27b2 ... user: drh tags: branch-3.53) | |
| 11:04 | In fts5, account for the possibility of negative docids when allocating a buffer to store the results of merging detail=none prefix lists. Fix for report 2026-08-04T08:49:27Z. (check-in: a7f8c92f62 ... user: dan tags: trunk) | |
|
2026-08-03
| ||
| 15:05 | When processing a vector IN(...) term in a WHERE clause, do not add individual terms for each column if the RHS of the IN(...) is a query that is expected to do the special min-max aggregate behaviour. Fix for 2026-08-03T09:05:06Z. (check-in: 0f873f5651 ... user: dan tags: trunk) | |
Changes
Modified ext/fts5/fts5_index.c
from [0e3877bc71]
to [0727c04457].
[diff]
Modified ext/fts5/test/fts5prefix2.test
from [a5bb43b8a2]
to [6cf99fe938].
[diff]