lang_reindex.html 2.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
  2. <html><head>
  3. <title>SQLite Query Language: REINDEX</title>
  4. <style type="text/css">
  5. body {
  6. margin: auto;
  7. font-family: Verdana, sans-serif;
  8. padding: 8px 1%;
  9. }
  10. a { color: #45735f }
  11. a:visited { color: #734559 }
  12. .logo { position:absolute; margin:3px; }
  13. .tagline {
  14. float:right;
  15. text-align:right;
  16. font-style:italic;
  17. width:240px;
  18. margin:12px;
  19. margin-top:58px;
  20. }
  21. .toolbar {
  22. font-variant: small-caps;
  23. text-align: center;
  24. line-height: 1.6em;
  25. margin: 0;
  26. padding:1px 8px;
  27. }
  28. .toolbar a { color: white; text-decoration: none; padding: 6px 12px; }
  29. .toolbar a:visited { color: white; }
  30. .toolbar a:hover { color: #80a796; background: white; }
  31. .content { margin: 5%; }
  32. .content dt { font-weight:bold; }
  33. .content dd { margin-bottom: 25px; margin-left:20%; }
  34. .content ul { padding:0px; padding-left: 15px; margin:0px; }
  35. /* rounded corners */
  36. .se { background: url(images/se.png) 100% 100% no-repeat #80a796}
  37. .sw { background: url(images/sw.png) 0% 100% no-repeat }
  38. .ne { background: url(images/ne.png) 100% 0% no-repeat }
  39. .nw { background: url(images/nw.png) 0% 0% no-repeat }
  40. </style>
  41. <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  42. </head>
  43. <body>
  44. <div><!-- container div to satisfy validator -->
  45. <a href="lang.html">
  46. <h2 align="center">SQL As Understood By SQLite</h2></a><h1>REINDEX</h1><h4><a href="syntaxdiagrams.html#reindex-stmt">reindex-stmt:</a></h4><blockquote> <img alt="syntax diagram reindex-stmt" src="images/syntax/reindex-stmt.gif"></img> </blockquote>
  47. <p>The REINDEX command is used to delete and recreate indices from scratch.
  48. This is useful when the definition of a collation sequence has changed.
  49. </p>
  50. <p>In the first form, all indices in all attached databases that use the
  51. named collation sequence are recreated. In the second form, if
  52. <i>&#91;database-name.&#93;table/index-name</i> identifies a table,
  53. then all indices
  54. associated with the table are rebuilt. If an index is identified, then only
  55. this specific index is deleted and recreated.
  56. </p>
  57. <p>If no <i>database-name</i> is specified and there exists both a table or
  58. index and a collation sequence of the specified name, then indices associated
  59. with the collation sequence only are reconstructed. This ambiguity may be
  60. dispelled by always specifying a <i>database-name</i> when reindexing a
  61. specific table or index.