Michael B. 8665df56e8 leveldb: fix table's data blocks' internal keys decoding ... In the LevelDB encoding, the internal key can be cut at any byte: including the user_key, type, or sequence_number. The resulting prefix is shared among subsequent keys and not specified explicitly by them. This fixes a previous mistaken belief that cuts can't happen in the last 8 bytes of the type & sequence number. Tests are added.		2023-12-08 23:37:10 +01:00
..
testdata	leveldb: fix table's data blocks' internal keys decoding	2023-12-08 23:37:10 +01:00
leveldb_descriptor.go	leveldb: fix table's data blocks' internal keys decoding	2023-12-08 23:37:10 +01:00
leveldb_descriptor.jq	leveldb: fix metaindex keys, refactoring, and jq syntax per PR	2023-12-07 17:11:55 +01:00
leveldb_descriptor.md	leveldb: add torepr for descriptor	2023-12-07 12:43:55 +01:00
leveldb_log.go	leveldb: fix metaindex keys, refactoring, and jq syntax per PR	2023-12-07 17:11:55 +01:00
leveldb_log.md	leveldb: improve log documentation	2023-12-07 14:36:47 +01:00
leveldb_table.go	leveldb: fix table's data blocks' internal keys decoding	2023-12-08 23:37:10 +01:00
leveldb_table.md	leveldb: add log and descriptor decoders	2023-12-06 19:24:49 +01:00