EVL – ETL Tool

Products, services and company names referenced in this document may be either trademarks or registered trademarks of their respective owners.

Copyright © 2017–2023 EVL Tool, s.r.o.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts.

Table of Contents


(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.


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).


  <f_in> [<database>.]<table> (<evd>|-d <inline_evd>)
  [-x|--text-input] [-a|--append]

evl writesqlite
  [<database>.]<table> (<evd>|-d <inline_evd>)
  [-x|--text-input] [-a|--append]

evl writesqlite
  ( --help | --usage | --version )


-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’


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:


print this help and exit


print short usage information and exit

-v, --verbose

print to stderr info/debug messages of the component


print version and exit