Writesqlite
(since EVL 2.7)
Write stdin or <f_in>
into SQLite <table>
. If the table is not empty, it is truncated
unless ‘--append’ option is used.
Path to the database file is taken from environment variable ‘$EVL_SQLITE_DATABASE’, unless
<db_file>
is specified.
- Writesqlite
-
is to be used in EVS job structure definition file.
<f_in>
is either input file or flow name. - evl writesqlite
-
is intended for standalone usage, i.e. to be invoked from command line and reading records from standard input.
EVD and EVS are EVL definition files, for details see evl-evd(5) and evl-evs(5).
Synopsis
Writesqlite <f_in> [<database>.]<table> (<evd>|-d <inline_evd>) [-x|--text-input] [-a|--append] [--dbname=<db_file>] evl writesqlite [<database>.]<table> (<evd>|-d <inline_evd>) [-x|--text-input] [-a|--append] [--dbname=<db_file>] [-v|--verbose] evl writesqlite ( --help | --usage | --version )
Options
- -a, --append
-
target table is appended, not truncated
- -d, --data-definition=<inline_evd>
-
either this option or the file <evd> must be presented. Example: -d ’id int, name string, started timestamp’
- --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’.
- -x, --text-input
-
suppose the input as text, not binary
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