[sqlite] Version 3.8.9 is in testing

[R.Smith]

Ugh, the text-only formatter messed that up, let's try again:

> Suggested  (changes in *...*):
>
> PRAGMA database.index_xinfo(index-name);
>
> This pragma returns information about every column in an index. Unlike 
> *the* index_info pragma, this pragma returns information about *all 
> columns used* in the index *and not only* the key columns. (A key 
> column is a column that is actually named in *the CREATE INDEX, UNIQUE 
> constraint or PRIMARY KEY constraint statement which created the 
> index*. Auxiliary columns are additional columns needed to locate the 
> table entry that corresponds to each index entry.)
>
> Output columns from the index_xinfo pragma are as follows:
>
> 1. The rank of the column within the index. (0 means left-most. Key 
> columns come before auxiliary columns.)
> 2. The rank of the column within *the table, or -1 if the column is 
> the rowid of the table being indexed*.
> 3. The name of the column being indexed, or NULL *if the column is the 
> rowid of the table being indexed*.
> 4. 1 if the *column is sorted in reverse order (DESC) in the index, 
> or* 0 otherwise.
> 5. The name for the collating sequence used to compare values in the 
> index-column.
> 6. 1 if the *column is a key column, or 0 if it is an auxiliary column*.

[sqlite] Version 3.8.9 is in testing

[R.Smith]

Some small legibility / continuity change suggestions to the new 
index_xinfo pragma doc:

Original:

*PRAGMA */database./*index_xinfo(*/index-name/*);*

This pragma returns information about every column in an index. Unlike 
this index_info pragma 
, this pragma 
returns information about every column in the index, not just the key 
columns. (A key column is a column that is actually named in the CREATE 
INDEX  index 
statement or UNIQUE constraint 
 or 
PRIMARY KEY constraint 
 that 
created the index. Auxiliary columns are additional columns needed to 
locate the table entry that corresponds to each index entry.)

Output columns from the index_xinfo pragma are as follows:

 1. The rank of the column within the index. (0 means left-most. Key
columns come before auxiliary columns.)
 2. The rank of the column within the table being indexed, or -1 if the
index-column is the rowid
 of the
table being indexed.
 3. The name of the column being indexed, or NULL if the index-column is
the rowid 
of the table being indexed.
 4. 1 if the index-column is sorted in reverse (DESC) order by the index
and 0 otherwise.
 5. The name for the collating sequence
 used to
compare values in the index-column.
 6. 1 if the index-column is a key column and 0 if the index-column is
an auxiliary column


Suggested  (changes in *...*):

*PRAGMA */database./*index_xinfo(*/index-name/*);*

This pragma returns information about every column in an index. Unlike 
*the* index_info pragma 
, this pragma 
returns information about *all columns used* in the index *and not only* 
the key columns. (A key column is a column that is actually named in 
*the CREATE INDEX , 
UNIQUE constraint 
 or 
PRIMARY KEY constraint 
 
statement which created the index*. Auxiliary columns are additional 
columns needed to locate the table entry that corresponds to each index 
entry.)

Output columns from the index_xinfo pragma are as follows:

 1. The rank of the column within the index. (0 means left-most. Key
columns come before auxiliary columns.)
 2. The rank of the column within *the table, or -1 if the column is the
rowid  of
the table being indexed*.
 3. The name of the column being indexed, or NULL *if the column is the
rowid  of
the table being indexed*.
 4. 1 if the *column is sorted in reverse order (DESC) in the index, or*
0 otherwise.
 5. The name for the collating sequence
 used to
compare values in the index-column.
 6. 1 if the *column is a key column, or 0 if it is an auxiliary column*.

[sqlite] Version 3.8.9 is in testing

[Richard Hipp]

On 4/2/15, Richard Hipp  wrote:
> SQLite version 3.8.9 is now in testing.  When the status board at
> https://www.sqlite.org/checklists/3080900/index goes all green, we
> will cut the release.

The release has been postponed due to an obscure problem that testing
revealed on OS-X.  The problem is related to file locking and only
seems to occur on OS-X.  (See the importance of cross-platform
testing!)  We will need to chase this problem to ground and then
restart the testing effort from the beginning.  So this is likely to
mean a long delay before the 3.8.9 release.

-- 
D. Richard Hipp
drh at sqlite.org

[sqlite] Version 3.8.9 is in testing

[Jan Nijtmans]

2015-04-02 15:15 GMT+02:00 Richard Hipp :
> A draft of the 3.8.9 website is found at http://www.sqlite.org/draft/
> and in particular the change log can be seen at
> https://www.sqlite.org/draft/releaselog/3_8_9.html

I would have expected to find this change somewhere in the
release log:



Regards,
Jan Nijtmans

[sqlite] Version 3.8.9 is in testing

[Richard Hipp]

SQLite version 3.8.9 is now in testing.  When the status board at
https://www.sqlite.org/checklists/3080900/index goes all green, we
will cut the release.  If you have any concerns about the current
code, please speak up soon!

A draft of the 3.8.9 website is found at http://www.sqlite.org/draft/
and in particular the change log can be seen at
https://www.sqlite.org/draft/releaselog/3_8_9.html

-- 
D. Richard Hipp
drh at sqlite.org