/ Check-in [da9a2e5a]
Login

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

Overview
Comment:Fix formatting errors in the previous commit.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | schemalint
Files: files | file ages | folders
SHA3-256: da9a2e5aa977f7e8e9e4365f7b34bb4f482029a3d44646100773cedc8ea9b959
User & Date: dan 2017-04-21 19:56:53
Context
2017-04-21
19:58
Another minor formatting fix. check-in: 9fa2ce3c user: dan tags: schemalint
19:56
Fix formatting errors in the previous commit. check-in: da9a2e5a user: dan tags: schemalint
19:53
Update the README.md file in the ext/expert/ directory. check-in: 3b2ff4e0 user: dan tags: schemalint
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to ext/expert/README.md.

     1      1   ## SQLite Expert Extension
     2      2   
     3      3   This folder contains code for a simple system to propose useful indexes
     4      4   given a database and a set of SQL queries. It works as follows:
     5      5   
     6      6     1. The user database schema is copied to a temporary database.
     7      7   
     8         -  1. All SQL queries are prepared against the temporary database. I
            8  +  1. All SQL queries are prepared against the temporary database.
     9      9        Information regarding the WHERE and ORDER BY clauses, and other query
    10         -     features that affect index selection, are recorded.
           10  +     features that affect index selection are recorded.
    11     11   
    12         -  1. The information gathered in step 2 is used to create (possibly a large
    13         -     number of) candidate indexes.
           12  +  1. The information gathered in step 2 is used to create candidate indexes
           13  +     - indexes that the planner might have made use of in the previous step,
           14  +     had they been available.
    14     15   
    15     16     1. A subset of the data in the user database is used to generate statistics
    16     17        for all existing indexes and the candidate indexes generated in step 3
    17     18        above.
    18     19   
    19     20     1. The SQL queries are prepared a second time. If the planner uses any
    20     21        of the indexes created in step 3, they are recommended to the user.
................................................................................
    63     64   
    64     65   Or an entire text file worth of queries with:
    65     66   
    66     67   <pre>
    67     68     ./sqlite3_expert -file &lt;text-file&gt; test.db
    68     69   </pre>
    69     70   
    70         -By default, sqlite3_expert generates index statistics using all the data in
           71  +By default, sqlite3\_expert generates index statistics using all the data in
    71     72   the user database. For a large database, this may be prohibitively time
    72         -consuming. The "-sample" option may be used to configure sqlite3_expert to
           73  +consuming. The "-sample" option may be used to configure sqlite3\_expert to
    73     74   generate statistics based on an integer percentage of the user database as
    74     75   follows:
    75     76   
    76     77   <pre>
    77     78     # Generate statistics based on 25% of the user database rows:
    78     79     ./sqlite3_expert -sample 25 -sql &lt;sql-query&gt; test.db
    79     80   
    80     81     # Do not generate any statistics at all:
    81     82     ./sqlite3_expert -sample 0 -sql &lt;sql-query&gt; test.db
    82     83   </pre>