cdb(1)
β¨ NAME β¨
okay so bestie, this is the cdb(1) page, and the actual main character is cdbtest β literally βcheck a constant database.β π
π¦ SYNOPSIS π¦
cdbtest
π DESCRIPTION π
cdbtest reads a (seekable) constant database from its standard input. Like, standard input, bestie β thatβs the vibe. πΈ
For each record in the database, it double-checks that the record can be found by its key. Then it prints tallies in several categories:
- found β the number of records found correctly by their keys. Slay. β¨
- different record β the number of records where a different record was found with the same key. This should not happen unless the database has multiple records with the same key. So yeah, duplicate-key situation, iykyk. π
- bad length β the number of records found but with the wrong data length. This should never happen. Periodt. π
- not found β the number of records not found. This should never happen either. Not even once. π
- untested β the number of records with keys longer than
1024bytes.cdbtestdoesnβt bother testing these records. Itβs giving βnot my problemβ energy, honestly. π
There is also a cdb64test that uses cdb64 format instead of cdb format. Cute twin behavior. π«Ά
π SEE ALSO π
cdbget(1), cdbmake(1), cdbstats(1)
thatβs the whole page, bestie β the footer/source line is literally just cdb(1) again, with no extra version or date drama, so this is the full iconic minimal situation. mwah ππ
π¦ where this page comes from
- nixpkgs unstable: cdb 20251021
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms