Documentation Source Text

Check-in Differences
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Difference From 72fd502948968ef0 To 978ca626bdc5f151

2022-01-22
21:20
Swat grammar nit in last checkin. (check-in: e40159680c user: larrybr tags: trunk)
21:05
Take dot-command arg-parsing clarification (check-in: 978ca626bd user: larrybr tags: trunk)
20:55
Clarify dot-command argument parsing (check-in: a7d5cbe876 user: larrybr tags: branch-3.37)
18:30
Clarify .expert option noted in https://sqlite.org/forum/forumpost/745f7e63b3 (check-in: 7e61bb09e2 user: larrybr tags: branch-3.37)
17:02
Clarify .expert option noted in https://sqlite.org/forum/forumpost/745f7e63b3 (check-in: 72fd502948 user: larrybr tags: trunk)
2022-01-21
19:26
Add requirements marks to newer parts of the date/time documentation. (check-in: deb6d14033 user: drh tags: trunk)

Changes to pages/cli.in.

235
236
237
238
239
240
241
242





243







244
245
246

247
248
249
250
251
252
253
<li>A dot-command cannot occur in the middle of an ordinary SQL
    statement.  In other words, a dot-command cannot occur at a
    continuation prompt.
<li>Dot-commands do not recognize comments.
</ul>

<p>The arguments passed to dot-commands are parsed from the command tail, 
per these rules: Arguments are delimited by whitespace (excluding newline); 





Text bounded by a pair of single-quotes or double-quotes is treated as a 







single argument, with the quotes stripped.
Within a double-quoted argument, traditional C-string literal, 
backslash escape sequence translation is done.


<p>The dot-commands
are interpreted by the sqlite3.exe command-line program, not by
SQLite itself.  So none of the dot-commands will work as an argument
to SQLite interfaces like [sqlite3_prepare()] or [sqlite3_exec()].

<tcl>hd_fragment dotmode {.mode} {output mode}</tcl>







|
>
>
>
>
>
|
>
>
>
>
>
>
>
|
|
|
>







235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
<li>A dot-command cannot occur in the middle of an ordinary SQL
    statement.  In other words, a dot-command cannot occur at a
    continuation prompt.
<li>Dot-commands do not recognize comments.
</ul>

<p>The arguments passed to dot-commands are parsed from the command tail, 
per these rules:<br>
(1) The trailing newline and any other trailing whitespace is discarded;<br>
(2) Whitespace immediately following the dot-command name or an argument
input end bound is discarded;<br>
(3) An argument input begins with any non-whitespace character;<br>
(4) An argument input end bound depends upon its leading character thusly:<br>
&nbsp;(4.a) for a leading single-quote ('), a single-quote acts
as the end bound;<br>
&nbsp;(4.b) for a leading double-quote ("), a unescaped double-quote
 acts as the end bound;<br>
&nbsp;(4.c) for any other leading character, the end bound is
 any whitespace; and<br>
&nbsp;(4.d) the command tail end acts as the end bound for any argument;<br>
(5) Within a double-quoted argument input, a backslash-escaped double-quote
 is part of the argument rather than its terminating quote;<br>
(6) Within a double-quoted argument, traditional C-string literal, backslash
 escape sequence translation is done; and<br>
(7) for quote-bounded argument inputs, the bounding quotes are stripped.<br>

<p>The dot-commands
are interpreted by the sqlite3.exe command-line program, not by
SQLite itself.  So none of the dot-commands will work as an argument
to SQLite interfaces like [sqlite3_prepare()] or [sqlite3_exec()].

<tcl>hd_fragment dotmode {.mode} {output mode}</tcl>