#701 closed defect (fixed)
Where to store which values exist in a document?
| Reported by: | Olly Betts | Owned by: | Olly Betts |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.0.0 |
| Component: | Backend-Honey | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Operating System: | All |
Description
(Split out of #181)
Current backends store the list of which values are used in each document in the termlist table, so things like iterating the values in a document require it.
As I said in #181, I'm not sure if this argues for putting this data elsewhere or not. If not, we should document this clearly in the appropriate places.
Marking for 1.4.x, in case we just want to document this. If it needs a storage change, it's something for glass+1.
Change History (2)
comment:1 by , 8 years ago
| Component: | Backend-Glass → Backend-Honey |
|---|---|
| Milestone: | 1.4.x → 1.5.0 |
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Honey (merged to git master recently) stores this data in the same entry as the termlist. For the common case of only values slots up to at most slot 6 (inclusive) being set (including the case where no values are set) this only takes a single byte.