Changes between Version 4 and Version 5 of FlintValueTable


Ignore:
Timestamp:
21/08/08 12:21:11 (17 years ago)
Author:
Olly Betts
Comment:

Update for 1.0.7

Legend:

Unmodified
Added
Removed
Modified
  • FlintValueTable

    v4 v5  
    55== Key Format ==
    66
    7 Quartz stores the key as: lsb ... msb of the docid, until all remaining bytes are zero
     7{{{
     8pack_uint_preserving_sort(docid)
     9}}}
    810
    9 Flint currently uses pack_uint_preserving_sort(docid) - this takes one extra byte compared to
     11This takes one extra byte compared to
    1012Quartz, but means that when appending documents to a database, the insert is always
    1113in the same place (at the "end" of the table).  This is faster, and produces a more compact
    1214database without a separate compaction step.
    1315
    14 (The eventual plan is to subclass the compare routine so we can store the key
    15 as compactly as Quartz does but keep the improved sort order.)
     16The plan for chert or later is to subclass the compare routine so we can store the key
     17as compactly as Quartz did but keep the improved sort order.
    1618
    1719== Tag Format ==
    1820
    19 Currently the tag is stored exactly in the same way as Quartz.
     21Zero or more of (in ascending slot order):
     22
     23{{{
     24pack_uint(slot) +
     25pack_string(value)
     26}}}
     27
     28
     29