.B sqlcipher

\- A command line interface for SQLCipher version 3

.B sqlcipher

.RI [ options ]

.RI [ databasefile ]

.RI [ SQL ]

.PP

.B sqlcipher

is a terminal-based front-end to the SQLCipher library that can evaluate

queries interactively and display the results in multiple formats.

.B sqlcipher

can also be used within shell scripts and other applications to provide

batch processing features.

To start a

.B sqlcipher

interactive session, invoke the

.B sqlcipher

command and optionally provide the name of a database file. If the

database file does not exist, it will be created. If the database file

does exist, it will be opened.

For example, to create a new database file named "mydata.db", create

a table named "memos" and insert a couple of records into that table:

.sp

$

.B sqlcipher mydata.db

.br

SQLite version 3.43.0 2023-08-11 17:45:23

.br

Enter ".help" for usage hints.

.br

sqlite>

.B create table memos(text, priority INTEGER);

.br

sqlite>

.B insert into memos values('deliver project description', 10);

.br

sqlite>

.B insert into memos values('lunch with Christine', 100);

.br

sqlite>

.B select * from memos;

.br

deliver project description|10

.br

lunch with Christine|100

.br

sqlite>

.sp

If no database name is supplied, the ATTACH sql command can be used

to attach to existing or create new database files. ATTACH can also

be used to attach to multiple databases within the same interactive

session. This is useful for migrating data between databases,

possibly changing the schema along the way.

Optionally, a SQL statement or set of SQL statements can be supplied as

a single argument. Multiple statements should be separated by

semi-colons.

For example:

.sp

$

.B sqlcipher -line mydata.db 'select * from memos where priority > 20;'

.br

text = lunch with Christine

.br

priority = 100

.br

.sp

.PP

The interactive interpreter offers a set of meta-commands that can be

used to control the output format, examine the currently attached

database files, or perform administrative operations upon the

attached databases (such as rebuilding indices). Meta-commands are

always prefixed with a dot (.).

A list of available meta-commands can be viewed at any time by issuing

the '.help' command. For example:

.sp

sqlite>

.B .help

.nf

.tr %.

...

.sp

.fi

<<<<<<< HEAD:sqlcipher.1

.B sqlcipher

has the following options:

.TP

Stop after hitting an error.

.TP

Force batch I/O.

.TP

Query results will be displayed in a table like form, using

whitespace characters to separate the columns and align the

output.

.TP

run

.I command

before reading stdin

.TP

Set output mode to CSV (comma separated values).

.TP

Print commands before execution.

.TP

Read and execute commands from

.I file

, which can contain a mix of SQL statements and meta-commands.

.TP

Turn headers on or off.

.TP

Show help on options and exit.

.TP

Query results will be output as simple HTML tables.

.TP

Force interactive I/O.

.TP

Query results will be displayed with one value per line, rows

separated by a blank line. Designed to be easily parsed by

scripts or other programs

.TP

Query results will be displayed with the separator (|, by default)

character between each field value. The default.

.TP

Set default mmap size to

.I N

.TP

Set string used to represent NULL values. Default is ''

(empty string).

.TP

Set output field separator. Default is '|'.

.TP

Print memory stats before each finalize.

.TP

Show SQLite version.

.TP

Use

.I name

as the default VFS.

=======

The available commands differ by version and build options, so they

are not listed here. Please refer to your local copy for all available

options.

>>>>>>> sqlite-release:sqlite3.1

.B sqlcipher

reads an initialization file to set the configuration of the

interactive environment. Throughout initialization, any previously

specified setting can be overridden. The sequence of initialization is

as follows:

o The default configuration is established as follows:

.sp

.nf

.cc |

mode = LIST

separator = "|"

main prompt = "sqlite> "

continue prompt = " ...> "

|cc .

.sp

.fi

o If the file

.B ${XDG_CONFIG_HOME}/sqlite3/sqliterc

or

.B ~/.sqliterc

exists, the first of those to be found is processed during startup.

It should generally only contain meta-commands.

o If the -init option is present, the specified file is processed.

o All other command line options are processed.

<<<<<<< HEAD:sqlcipher.1

https://www.zetetic.net/sqlcipher

=======

https://sqlite.org/cli.html

.br

https://sqlite.org/fiddle (a WebAssembly build of the CLI app)

>>>>>>> sqlite-release:sqlite3.1

.br

The sqlite3-doc package.

This manual page was originally written by Andreas Rottmann

<rotty@debian.org>, for the Debian GNU/Linux system (but may be used

by others). It was subsequently revised by Bill Bumgarner <bbum@mac.com>,

Laszlo Boszormenyi <gcs@debian.hu>, and the sqlite3 developers.