Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Update to the ".parameter" command documentation to conform to the latest implementation. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
9dab48bb9d22480d68d3e109a737babc |
| User & Date: | drh 2019-03-26 00:14:39.518 |
Context
|
2019-03-26
| ||
| 13:11 | Update window functions documentation. (check-in: bdc2a67078 user: dan tags: trunk) | |
| 00:14 | Update to the ".parameter" command documentation to conform to the latest implementation. (check-in: 9dab48bb9d user: drh tags: trunk) | |
|
2019-03-25
| ||
| 20:56 | Updates to the change log for 3.28.0. (check-in: 32b82e8386 user: drh tags: trunk) | |
Changes
Changes to pages/cli.in.
| ︙ | ︙ | |||
1050 1051 1052 1053 1054 1055 1056 |
<p>Parameters can be either named or unnamed. An unnamed parameter is a single
question mark ("?"). Named parameters are a "?" followed immediately by a number
(ex: "?15" or "?123") or one of the characters "$", ":", or "@" followed by an
alphanumeric name (ex: "$var1", ":xyz", "@bingo").
<p>This command-line shell leaves unnamed parameters unbound, meaning that they
will have a value of an SQL NULL, but named parameters might be assigned values.
| | | | | | | > > > > > > > > | 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 |
<p>Parameters can be either named or unnamed. An unnamed parameter is a single
question mark ("?"). Named parameters are a "?" followed immediately by a number
(ex: "?15" or "?123") or one of the characters "$", ":", or "@" followed by an
alphanumeric name (ex: "$var1", ":xyz", "@bingo").
<p>This command-line shell leaves unnamed parameters unbound, meaning that they
will have a value of an SQL NULL, but named parameters might be assigned values.
If there exists a TEMP table named "sqlite_parameters" with a schema like this:
<codeblock>
CREATE TEMP TABLE sqlite_parameters(
key TEXT PRIMARY KEY,
value ANY
) WITHOUT ROWID;
</codeblock>
<p>And if there is a entry in that table where the key column exactly matches
the name of parameter (including the initial "?", "$", ":", or "@" character)
then the parameter is assigned the value of the value column. If no entry exists,
the parameter defaults to NULL.
<p>The ".parameter" command exists to simplify managing this table. The
".parameter init" command (often abbreviated as just ".param init") creates
the temp.sqlite_parameters table if it does not already exist. The ".param list"
command shows all entries in the temp.sqlite_parameters table. The ".param clear"
command drops the temp.sqlite_parameters table. The ".param set KEY VALUE" and
".param unset KEY" commands create or delete entries from the
temp.sqlite_parameters table.
<p>The temp.sqlite_parameters table only provides values for parameters in the
command-line shell. The temp.sqlite_parameter table has no affect on queries
that are run directly using the SQLite C-language API. Individual applications
are expected to implement their own parameter binding. You can search for
"sqlite_parameters" in the
[https://sqlite.org/src/file/src/shell.c.in|command-line shell source code]
to see how the command-line shell does parameter binding, and use that as
a hint for how to implement it yourself.
<tcl>hd_fragment expert {.expert command}</tcl>
<h1>Index Recommendations (SQLite Expert)</h1>
<p><b>Note: This command is experimental. It may be removed or the
interface modified in incompatible ways at some point in the future.
|
| ︙ | ︙ |