Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Further tweaks to the cli.html document. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
c27765f3b79b431983ef2cf30fbe7710 |
User & Date: | drh 2018-01-10 19:39:00.642 |
Context
2018-01-10
| ||
20:28 | Add the "Export to Excel" subparagraph under "CSV Export" section of the CLI documentation. (check-in: 1728ebf59c user: drh tags: trunk) | |
19:39 | Further tweaks to the cli.html document. (check-in: c27765f3b7 user: drh tags: trunk) | |
19:26 | Improved documentation for recently added features such as SQL Archive support and the Zipfile extension. (check-in: 260f2fd7ee user: drh tags: trunk) | |
Changes
Changes to pages/cli.in.
1 2 3 4 5 6 7 8 | <title>Command Line Shell For SQLite</title> <tcl>hd_keywords {CLI} {Command Line Interface} {command-line shell} \ {command-line interface} </tcl> <table_of_contents> <tcl>hd_fragment intro</tcl> <h1>Getting Started</h1> | | | | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 | <title>Command Line Shell For SQLite</title> <tcl>hd_keywords {CLI} {Command Line Interface} {command-line shell} \ {command-line interface} </tcl> <table_of_contents> <tcl>hd_fragment intro</tcl> <h1>Getting Started</h1> <p>The SQLite project provides a simple command-line program named <b>sqlite3</b> (or <b>sqlite3.exe</b> on Windows) that allows the user to manually enter and execute SQL statements against an SQLite database. This document provides a brief introduction on how to use the <b>sqlite3</b> program. <p>Start the <b>sqlite3</b> program by typing "sqlite3" at the command prompt, optionally followed by the name the file that holds the SQLite database. If the named file does not exist, a new database file with the given name will be created automatically. If no database file is specified on the command-line, a temporary database is created, then deleted when the "sqlite3" program exits. <p>On startup, the <b>sqlite3</b> program will show a brief banner message then prompt you to enter SQL. Type in SQL statements (terminated |
︙ | ︙ | |||
55 56 57 58 59 60 61 | sqlite> (((select * from tbl1;))) hello!|10 goodbye|20 sqlite> } </tclscript> | | | 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 | sqlite> (((select * from tbl1;))) hello!|10 goodbye|20 sqlite> } </tclscript> <p>Terminate the sqlite3 program by typing your system End-Of-File character (usually a Control-D). Use the interrupt character (usually a Control-C) to stop a long-running SQL statement.</p> <p>Make sure you type a semicolon at the end of each SQL command! The sqlite3 program looks for a semicolon to know when your SQL command is complete. If you omit the semicolon, sqlite3 will give you a continuation prompt and wait for you to enter more text to be |
︙ | ︙ | |||
97 98 99 100 101 102 103 | Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> (((.open ex1.db))) sqlite> }</tclscript> <p>The example above causes the database file named "ex1.db" to be opened | | > | 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 | Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> (((.open ex1.db))) sqlite> }</tclscript> <p>The example above causes the database file named "ex1.db" to be opened and used. The "ex1.db" file is created if it does not previously exist. You might want to use a full pathname to ensure that the file is in the directory that you think it is in. Use forward-slashes as the directory separator character. In other words use "c:/work/ex1.db", not "c:\work\ex1.db".</p> <p>Alternatively, you can create a new database using the default temporary storage, then save that database into a disk file using the ".save" command: |
︙ | ︙ | |||
139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 | <p> For a listing of the available dot commands, you can enter ".help" at any time. For example: </p> <tclscript>DisplayCode { sqlite> (((.help))) .auth ON|OFF Show authorizer callbacks .backup ?DB? FILE Backup DB (default "main") to FILE .bail on|off Stop after hitting an error. Default OFF .binary on|off Turn binary output on or off. Default OFF .cd DIRECTORY Change the working directory to DIRECTORY .changes on|off Show number of rows changed by SQL .check GLOB Fail if output since .testcase does not match .clone NEWDB Clone data into NEWDB from the existing database .databases List names and files of attached databases .dbinfo ?DB? Show status information about the database .dump ?TABLE? ... Dump the database in an SQL text format If TABLE specified, only dump tables matching LIKE pattern TABLE. .echo on|off Turn command echo on or off .eqp on|off|full Enable or disable automatic EXPLAIN QUERY PLAN .exit Exit this program .fullschema ?--indent? Show schema and the content of sqlite_stat tables .headers on|off Turn display of headers on or off .help Show this message .import FILE TABLE Import data from FILE into TABLE .imposter INDEX TABLE Create imposter table TABLE on index INDEX .indexes ?TABLE? Show names of all indexes If TABLE specified, only show indexes for tables | > > | 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 | <p> For a listing of the available dot commands, you can enter ".help" at any time. For example: </p> <tclscript>DisplayCode { sqlite> (((.help))) .archive ... Manage SQL archives: ".archive --help" for details .auth ON|OFF Show authorizer callbacks .backup ?DB? FILE Backup DB (default "main") to FILE .bail on|off Stop after hitting an error. Default OFF .binary on|off Turn binary output on or off. Default OFF .cd DIRECTORY Change the working directory to DIRECTORY .changes on|off Show number of rows changed by SQL .check GLOB Fail if output since .testcase does not match .clone NEWDB Clone data into NEWDB from the existing database .databases List names and files of attached databases .dbinfo ?DB? Show status information about the database .dump ?TABLE? ... Dump the database in an SQL text format If TABLE specified, only dump tables matching LIKE pattern TABLE. .echo on|off Turn command echo on or off .eqp on|off|full Enable or disable automatic EXPLAIN QUERY PLAN .exit Exit this program .expert EXPERIMENTAL. Suggest indexes for specified queries .fullschema ?--indent? Show schema and the content of sqlite_stat tables .headers on|off Turn display of headers on or off .help Show this message .import FILE TABLE Import data from FILE into TABLE .imposter INDEX TABLE Create imposter table TABLE on index INDEX .indexes ?TABLE? Show names of all indexes If TABLE specified, only show indexes for tables |
︙ | ︙ | |||
760 761 762 763 764 765 766 | generates tests to verify that a subset of the tables are unchanged, simply run ".selftest --init" then [DELETE] the selftest rows that refer to tables that are not constant. <tcl>hd_fragment sqlar {SQL Archive} {.archive command}</tcl> <h1>SQLAR Archive Support</h1> | | | 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 | generates tests to verify that a subset of the tables are unchanged, simply run ".selftest --init" then [DELETE] the selftest rows that refer to tables that are not constant. <tcl>hd_fragment sqlar {SQL Archive} {.archive command}</tcl> <h1>SQLAR Archive Support</h1> <p>The ".archive" dot-command (often abbreviated as ".ar") provides built-in support for the [https://sqlite.org/sqlar|SQLite ARchive format]. The interface is similar to that of the "tar" command on unix systems. Each invocation of the ".ar" command must specify a single command option. The following commands are available: <table striped=1> |
︙ | ︙ |