KYUA-DB-MIGRATE(1)

KYUA-DB-MIGRATE(1) 💅

okay bestie, welcome to kyua db-migrate from the General Commands Manual — she's the glow-up specialist for your results files and she's so good at her job 🎀

---

✨ NAME ✨

kyua db-migrate — upgrades the schema of an existing results file. it's giving database makeover, no cap 💖

---

🌸 SYNOPSIS 🌸

kyua db-migrate [--results-file file]

---

💜 DESCRIPTION 💜

so the kyua db-migrate command migrates the schema of an existing database to the latest version implemented in kyua(1). glow-up era fr fr ✨

⚠️ this operation is NOT reversible. like, no take-backs, periodt. however, a backup of the database is created in the same directory where the database lives — so you do have a safety net, thank god 😭🫶

the following subcommand options are recognized, bestie:

• --results-file path, -s path — specifies the results file to operate on. defaults to LATEST, which causes kyua db-migrate to automatically load the latest results file from the current test suite. iykyk 👑

the following values are accepted for that one:

• LATEST — requests the load of the latest results file available for the test suite rooted at the current directory. main character energy, she finds it herself 🦋
• Directory — requests the load of the latest results file available for the test suite rooted at the given directory 📁
• Test suite name — requests the load of the latest results file available for the given test suite 🌈
• Results identifier — requests the load of a specific results file. one specific file, very pick-me, we love her ⭐
• Explicit file name (aka everything else) — load the specified results file. just hand her the file, babe 💅

see “Results files” for more details ⬇️

---

🗂️ Results files 🗂️

results files contain, as their name implies, the results of the execution of a test suite. each test suite executed by kyua-test(1) generates a new results file, and such results files can be loaded later on by inspection commands such as kyua-report(1) to analyze their contents. it's literally a whole scrapbook of your test runs 📸

results files support identifier-based lookups and also path name lookups. the differences between the two are described below, bestie, stay with me 🧚

the default naming scheme for the results files provides simple support for identifier-based lookups and historical recording of test suite runs. each results file is given an identifier derived from the test suite that generated it and the time the test suite was run. Kyua can later look up results files by these fields. so organized of her 💅

the identifier follows this pattern:

<test_suite>.<YYYYMMDD>-<HHMMSS>-<uuuuuu>

where test_suite is the path to the root of the test suite that was run with all slashes replaced by underscores and YYYYMMDD-HHMMSS-uuuuuu is a timestamp with microsecond resolution. microseconds?? she's precise and she knows it 💀✨

when using the default naming scheme, results files are stored in the ~/.kyua/store/ subdirectory and each file holds a name of the form:

~/.kyua/store/results.<identifier>.db

results files are simple SQLite databases with the schema described in the /usr/share/kyua/store/schema_v?.sql files. for details on the schema, please refer to the heavily commented SQL file — yes bestie, go read the comments, they ate 🔥

---

🎀 EXIT STATUS 🎀

the kyua db-migrate command returns 0 on success or 1 if the migration fails. slay or sad, no in between 😭

additional exit codes may be returned as described in kyua(1). 👑

---

🌟 SEE ALSO 🌟

• kyua(1)

---

and that's the whole vibe check, bestie 🫶 this page is from Debian, dated October 13, 2014, and it lives in the General Commands Manual section — mwah, iconic, periodt 💖✨