Documentation Source Text

Check-in [c1c7b5e3d1]
Login

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

Overview
Comment:Add links from the requirements.html page into the matrix. Clarifications to the CREATE INDEX and REINDEX documentation.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: c1c7b5e3d1844c7644c22e1a7d5afeccb1c801b0
User & Date: drh 2015-09-11 22:51:21.934
Context
2015-09-15
12:37
Fix a typo in the JSON documentation. (check-in: 833012c6a9 user: drh tags: trunk)
2015-09-11
22:51
Add links from the requirements.html page into the matrix. Clarifications to the CREATE INDEX and REINDEX documentation. (check-in: c1c7b5e3d1 user: drh tags: trunk)
20:19
Update the requirements.html document to provide links into the matrix for each requirement. (check-in: a6da4c726a user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/lang.in.
︙︙
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761

Section {CREATE INDEX} createindex {{CREATE INDEX}}

RecursiveBubbleDiagram create-index-stmt
</tcl>

<p>^The CREATE INDEX command consists of the keywords "CREATE INDEX" followed
by the name of the new index, the keyword "ON", the name of a previously
created table that is to be indexed, and a parenthesized list of names of
columns in the table and/or expressions that are used for the index key.
If the optional WHERE clause is included, then the index is a "[partial index]".
</p>

<tcl>hd_fragment {descidx} {descending indices} {descending index} {descending indexes}</tcl>
<p>^Each column name or expression can be followed by one
of the "ASC" or "DESC" keywords to indicate sort order.
^The sort order may or may not be ignored depending








|
|








746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761

Section {CREATE INDEX} createindex {{CREATE INDEX}}

RecursiveBubbleDiagram create-index-stmt
</tcl>

<p>^The CREATE INDEX command consists of the keywords "CREATE INDEX" followed
by the name of the new index, the keyword "ON", the name of a previously
created table that is to be indexed, and a parenthesized list of table column
names and/or expressions that are used for the index key.
If the optional WHERE clause is included, then the index is a "[partial index]".
</p>

<tcl>hd_fragment {descidx} {descending indices} {descending index} {descending indexes}</tcl>
<p>^Each column name or expression can be followed by one
of the "ASC" or "DESC" keywords to indicate sort order.
^The sort order may or may not be ignored depending
︙︙
3289
3290
3291
3292
3293
3294
3295

3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306

all indices in all attached databases that use the named collation sequences
are recreated. 

<p>^Or, if the argument attached to the REINDEX identifies a specific 
database table, then all indices attached to the database table are rebuilt. 
^If it identifies a specific database index, then just that index is recreated.


<p>^If no <yyterm>schema-name</yyterm> is specified and 
there exists both a table or
index and a collation sequence of the specified name, SQLite interprets
this as a request to rebuild the indices that use the named collation sequence.
This ambiguity in the syntax may be avoided by always specifying a
<yyterm>schema-name</yyterm> when reindexing a specific table or index.

<tcl>
###############################################################################
Section REPLACE replace REPLACE









>
|
<
|
<








3289
3290
3291
3292
3293
3294
3295
3296
3297

3298

3299
3300
3301
3302
3303
3304
3305

all indices in all attached databases that use the named collation sequences
are recreated. 

<p>^Or, if the argument attached to the REINDEX identifies a specific 
database table, then all indices attached to the database table are rebuilt. 
^If it identifies a specific database index, then just that index is recreated.

<p>^For a command of the form "REINDEX <i>name</i>", a match
against <yyterm>collation-name</yyterm> takes precedence over a match

against <yyterm>index-name</yyterm> or <yyterm>table-name</yyterm>.

This ambiguity in the syntax may be avoided by always specifying a
<yyterm>schema-name</yyterm> when reindexing a specific table or index.

<tcl>
###############################################################################
Section REPLACE replace REPLACE
︙︙
Changes to pages/requirements.in.
︙︙
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142

  } else {
    hd_puts "<dd><p>$reqtext\n"
  }
  set ck [
    db eval {SELECT DISTINCT srccat || '/' || srcfile FROM evidence
             WHERE reqno=$reqno ORDER BY 1}
  ]
  hd_puts "<i>(source <a href=\"$srcfile\">$srcfile</a>"
  if {[llength $ck]>0} {
    hd_puts ", checked-by: [join $ck {, }]"
  }
  hd_puts ", matrix: <a href='$surl'>context</a>"
  hd_puts ", <a href='$durl'>detail</a>)</i>"
  hd_puts "</p></dd>\n\n"
}








|








128
129
130
131
132
133
134
135
136
137
138
139
140
141
142

  } else {
    hd_puts "<dd><p>$reqtext\n"
  }
  set ck [
    db eval {SELECT DISTINCT srccat || '/' || srcfile FROM evidence
             WHERE reqno=$reqno ORDER BY 1}
  ]
  hd_puts "<i>(source: <a href=\"$srcfile\">$srcfile</a>"
  if {[llength $ck]>0} {
    hd_puts ", checked-by: [join $ck {, }]"
  }
  hd_puts ", matrix: <a href='$surl'>context</a>"
  hd_puts ", <a href='$durl'>detail</a>)</i>"
  hd_puts "</p></dd>\n\n"
}
︙︙