Runsqlite
(since EVL 2.7)
Run SQL or sqlite3 commands from stdin or <f_in> and write result into stdout or
<f_out>. It returns output from ‘sqlite3’ as is, so for quering the table to get
formatted EVL output use ‘Readsqlite’ or ‘evl readsqlite’.
Path to the database file is taken from environment variable ‘$EVL_SQLITE_DATABASE’, unless
<db_file> is specified.
- Runsqlite
-
is to be used in EVS job structure definition file.
<f_out>is either output file or flow name. - evl runsqlite
-
is intended for standalone usage, i.e. to be invoked from command line and writing records to standard output.
EVD and EVS are EVL definition files, for details see evl-evd(5) and evl-evs(5).
Synopsis
Runsqlite <f_in> <f_out> [--dbname=<db_file>] [--sqlite=<sqlite_options>] evl runsqlite [--dbname=<db_file>] [--sqlite=<sqlite_options>] [-v|--verbose] evl runsqlite ( --help | --usage | --version )
Options
- --dbname=<db_file>
-
path to the SQLite database file; if this option is not used, database file is taken from environment variable ‘$EVL_SQLITE_DATABASE’.
- --sqlite=<sqlite_options>
-
all
<sqlite_options>is provided to ‘sqlite’ utility.
Standard options:
- --help
-
print this help and exit
- --usage
-
print short usage information and exit
- -v, --verbose
-
print to stderr info/debug messages of the component
- --version
-
print version and exit