Op 6 aug 2014, om 02:57 heeft Richard Hipp het volgende geschreven:
Version 3.8.6 was originally scheduled for September. But the
change log (
http://www.sqlite.org/draft/releaselog/current.html) is getting
rather long
and there are a number of important bug fixes. So we might try to get
3.8.6 out the door sooner rather than later.
Please test! Recent amalgamations are available on the download
page (
http://www.sqlite.org/download.html). Please compile your
applications use
the latest tip of trunk and let us know if you encounter any problems.
Please review the change log and speak up if you see anything amiss.
The status board (http://www.sqlite.org/checklists/3080600/index)
for the
3.8.6 release is now on-line. The usual rule applies: When the
check-list
goes all-green, we will cut the release. No check-list items have
been
marked off yet, but we might start marking them off later this week,
or
early next week.
Your feedback is greatly appreciated.
--
D. Richard Hipp
d...@sqlite.org
Hello, I have a case where a primary key index is no longer used where
it was used before. Below is a script to reproduce this and the ourput
in the new and old SQLite versions respectively. Tthis is a minimal
case, leaving out anything further makes the problem disappear. Thus
it is strange that:
- the problem starts occuring only wher GROUP BY is present
- the problem occurs only when there are at least two joins
- idem only when the join condition involves BETWEEN
Hope that this contributes to the final release.
Thanks, E.Pasma
.version
CREATE TABLE node (node INTEGER PRIMARY KEY,
minchild INTEGER,
maxchild INTEGER,
status CHAR NOT NULL)
;
explain query plan
SELECT s2.status
FROM node s0
JOIN node s1 ON s1.node BETWEEN s0.minchild AND s0.maxchild
JOIN node s2 ON s2.node BETWEEN s1.minchild AND s1.maxchild
WHERE s0.node = 0 --root node
GROUP BY s2.status
;
SQLite 3.8.6 2014-08-06 14:36:53
1202e9771f6d699dbf5268368108a3527d06d799
0|0|0|SEARCH TABLE node AS s0 USING INTEGER PRIMARY KEY (rowid=?)
0|1|1|SCAN TABLE node AS s1
0|2|2|SEARCH TABLE node AS s2 USING INTEGER PRIMARY KEY (rowid>? AND
rowid<?)
0|0|0|USE TEMP B-TREE FOR GROUP BY
SQLite 3.8.5 2014-06-02 11:26:33
9f18b303cd1bc5779d82669884f802c7889b4947
0|0|0|SEARCH TABLE node AS s0 USING INTEGER PRIMARY KEY (rowid=?)
0|1|1|SEARCH TABLE node AS s1 USING INTEGER PRIMARY KEY (rowid>? AND
rowid<?)
0|2|2|SEARCH TABLE node AS s2 USING INTEGER PRIMARY KEY (rowid>? AND
rowid<?)
0|0|0|USE TEMP B-TREE FOR GROUP BY
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
