VLTEST(1)

πŸ’– VLTEST(1) πŸ’–

okay bestie, welcome to vltest, part of the Quick Database Manager family (that's QDBM, and she's iconic). this whole page is the manual for the vltest command, so grab a strawberry drink and let's get into it πŸ“


✨ NAME ✨

vltest β€” test cases for QDBM Villa. literally just that. a lil test-suite gremlin for the Villa database engine 🧚


🌸 SYNOPSIS 🌸

vltest write [-int] [-cz|-cy|-cx] [-tune lrecmax nidxmax lcnum ncnum]
[-fbp num] name rnum
vltest read [-int] name
vltest rdup [-int] [-cz|-cy|-cx] [-cc] [-tune lrecmax nidxmax lcnum
ncnum] [-fbp num] name rnum pnum
vltest combo [-cz|-cy|-cx] name
vltest wicked [-c] [-cz|-cy|-cx] name rnum

five little modes, each one its own whole vibe πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so vltest is a utility for facility test and performance test. what that means in human words: you use it to check a database that was generated by the command, or to measure the execution time of the command. main character energy fr fr ⏱️

you run it in the following format. name specifies a database name. rnum specifies the number of the records. both of those are load-bearing, don't skip 'em.

πŸŽ€ vltest write [-int] [-cz|-cy|-cx] [-tune lrecmax nidxmax lcnum ncnum] [-fbp num] name rnum

store records with keys of 8 bytes. and the way they change? they go 00000001, 00000002, and so on forever, like a little count-up situation ✨

πŸŽ€ vltest read [-int] [-vc] name

retrieve all records of the database above. that's it. that's the whole thing. she reads πŸ‘‘

πŸŽ€ vltest rdup [-int] [-cz|-cy|-cx] [-cc] [-tune lrecmax nidxmax lcnum ncnum] [-fbp num] name rnum pnum

store records with partway duplicated keys using duplicate mode. note the extra pnum β€” she's built different, she takes one more argument than her sister 🫢

πŸŽ€ vltest combo [-cz|-cy|-cx] name

perform combination test of various operations. it's giving chaos, but make it structured 🌈

πŸŽ€ vltest wicked [-c] [-cz|-cy|-cx] name rnum

perform updating operations selected at random. yes, random. yes, "wicked" is the actual name. no cap πŸ’€


πŸ’… OPTIONS πŸ’…

options feature the following. every single one, bestie, i'm not skipping a thing:

  • -int β€” treat keys and values as objects of int, and use comparing function VL_CMPINT. basically: int mode, on, slay.
  • -cz β€” compress leaves in the database with ZLIB. tiny leaves, big savings 🌸
  • -cy β€” compress leaves in the database with LZO.
  • -cx β€” compress leaves in the database with BZIP2.
  • -vc β€” refer to volatile cache. lowkey my fave, it's fast.
  • -cc β€” select VL_DCAT or VL_DDUP at random. spin the wheel, choose your destiny 🎑
  • -tune lrecmax nidxmax lcnum ncnum β€” set tuning parameters. four numbers, one dream.
  • -fbp num β€” set the size of the free block pool.
  • -c β€” perform comparison test with map of Cabin. (Cabin is a whole other icon, iykyk.)
ok important: this command returns 0 on success, and another on failure. so zero = good, not-zero = we're crying 😭
also!! the environment variable QDBMDBGFD specifies the file descriptor to output the history of updating the variable dpecode. yeah, dpecode. it's a debugging thing. set it and you get the receipts 🧾

πŸ’œ SEE ALSO πŸ’œ

go read those too, they're the supporting cast and they ate ✨


🌟 AUTHOR 🌟

QDBM was written by Mikio Hirabayashi <mikio@fallabs.com>. legend behavior, honestly πŸ‘‘


and that's the whole page bestie!! this was the VLTEST(1) man page from the Quick Database Manager, dated 2005-06-01 β€” yeah she's vintage, she's a classic, she's still serving πŸ’– go write some records, drink some water, and remember: exit status 0 or it's over for you. periodt. πŸŽ€πŸ¦‹