cdb(1)

πŸ“¦ in nixpkgs unstable

✨ 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 1024 bytes. cdbtest doesn’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