opentrep-dbmgr(1)

📦
version 0.08.01 · 4 versions
, in epel 10

okay bestie, welcome to opentrep-dbmgr(1) from the General Commands Manual — the interactive little gremlin that manages your SQL database and wants you to thrive 💅✨

💖 NAME 💖

opentrep-dbmgr — interactive command-line utility to manage the SQL database (SQLite3 or MySQL). No cap, it's giving database-manager main character energy 👑.

✨ SYNOPSIS ✨

opentrep-dbmgr [--prefix] [-v|--version] [-h|--help] [-p|--porfile <POR-file-path>] [-d|--xapiandb <Xapian-travel-database-path>] [-t|--sqldbtype <SQL-database-type>] [-s|--sqldbconx <SQL-database-connection-string>] [-l|--log <path-to-output-log-file>]

🦋 DESCRIPTION 🦋

opentrep-dbmgr is a small program to manage the relational (SQL) database. For now, only SQLite3 and MariaDB/MySQL databases are supported 💖.

The file with the list of the OPTD-maintained POR (points of reference) may be parsed, and the corresponding content inserted into the SQL database. At the prompt, launch the help or tutorial command to heva more details — yes, the page says “heva,” we’re keeping the typo, periodt 😭.

okay so opentrep-dbmgr accepts the following options:

  • --prefix — show the Opentrep installation prefix 🎀
  • -v, --version — print the currently installed version of Opentrep on the standard output 💖
  • -h, --help — produce that message and show usage 🫶
  • -p, --porfile <POR-file-path> — path (directory and file name) of the file of POR (points of reference). Usually, the file is optd_por_public.csv, for which the latest version may be found in the OpenTravelData project on GitHub: https://github.com/opentraveldata/opentraveldata/tree/master/opentraveldata 🦋
  • -d, --xapiandb <Xapian-travel-database-path> — path (directory) to the Xapian travel database. The indexer creates the Xapian database, or overwrites it when it already exists. It materialises as a collection of data files within a directory usually named traveldb 🔥
  • -t, --sqldbtype <SQL-database-type> — SQL database type, e.g., nosql (no SQL database), sqlite, mysql 🌈
  • -s, --sqldbconx <SQL-database-connection-string> — SQL database connection string, e.g., ~/tmp/opentrep/sqlite_travel.db (for SQLite3), "db=trep_trep user=trep password=trep" (for MySQL) 💅
  • -l, --log <path-to-output-log-file> — path (absolute or relative) of the output log file 🍓

See the output of the opentrep-dbmgr --help command for default options 👀.

Once the program is launched, just type the help command to get the full list of all the possible commands and their parameters. Note that that program features the auto-completion of commands — yes, “that that” is in the source, and auto-completion is iconic ⭐.

🌸 EXAMPLES 🌸

With SQLite3 🎀

opentrep-dbmgr -t sqlite -s /tmp/opentrep/sqlite_travel.db

With MySQL 💜

opentrep-dbmgr -t mysql -s "db=trep_trep user=trep password=trep"

🔥 SEE ALSO 🔥

opentrep-indexer(1), opentrep-searcher(1), opentrep-config(1), opentrep-library(3) 🦋

💌 SUPPORT 💌

Please report any bugs to http://github.com/trep/opentrep/issues 🙈.

Copyright © 2009-2019 Denis Arnaud 💖

See the COPYING file for more information on the (LGPLv2+) license, or directly on Internet: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.

footer vibe check, bestie: the source/version is OpenTREP, Version 0.08.01 — and the footer’s date slot isn’t actually printed in this source page, so we’re not inventing one, periodt 😭💅

📦 where this page comes from