Am Dienstag, 11. Oktober 2016, 06:50:01 CEST schrieb Keith Medcalf: > This was fixed September 7. The fix appears in 3.14.2 and also on the > current 3.15.0.
Does that mean that 3.14.2 is supposed to give the "6, 5, 7" result in the last query? I am asking as that's the version I am using (installed from Debian/sid) and I get "1, 2, 3" here. > https://www.sqlite.org/releaselog/3_14_2.html > > The ORDER BY LIMIT optimization is not valid unless the inner-most IN > operator loop is actually used by the query plan. Ticket > https://sqlite.org/src/info/0c4df46116e90f92 > > > SQLite version 3.15.0 2016-10-10 14:48:36 > Enter ".help" for usage hints. > Connected to a transient in-memory database. > Use ".open FILENAME" to reopen on a persistent database. > sqlite> create table i (id integer primary key, flags integer); > sqlite> insert into i values (1,1),(2,1),(3,1),(4,1),(5,5),(6,6),(7,4); > sqlite> create table m (id integer); > sqlite> insert into m values (1),(2),(3),(4),(5),(6),(7); > sqlite> SELECT id FROM i WHERE id IN (SELECT id FROM m) ORDER BY flags DESC; > 6 > 5 > 7 > 1 > 2 > 3 > 4 > sqlite> SELECT id FROM i WHERE id IN (SELECT id FROM m) ORDER BY flags DESC > limit 3; 6 > 5 > 7 Tobias [...]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
