Packaged version of SQLite (3.5.9) returns incorrect results from SELECT DISTINCT query
Bug #296390 reported by
Jean-Paul Calderone
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Divmod Imaginary |
Invalid
|
Undecided
|
Unassigned | ||
txcomputegrid - twisted based compute grid |
Invalid
|
Undecided
|
Unassigned | ||
Debian |
Fix Released
|
Unknown
|
|||
sqlite3 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
exarkun@takkun:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
exarkun@takkun:~$ sqlite3
SQLite version 3.5.9
Enter ".help" for instructions
sqlite> CREATE TABLE foo(foo TEXT);
sqlite> INSERT INTO foo VALUES ('a');
sqlite> INSERT INTO foo VALUES ('b');
sqlite> CREATE INDEX foo_foo ON foo(foo);
sqlite> SELECT DISTINCT foo FROM foo WHERE foo IS NOT NULL;
b
sqlite>
The correct result would have been the rows for a and b, not just b. This bug is apparently fixed in a later release of SQLite.
Changed in debian: | |
status: | Unknown → Fix Released |
To post a comment you must log in.
The upstream bug report seems to be <http:// www.sqlite. org/cvstrac/ tktview? tn=3236>. It is marked as a duplicate of another ticket which doesn't seem as related, but I'm sure the SQLite contributor who marked it as such is more familiar with the codebase than I. In any case, applying the diff in the revision linked from that ticket to the 3.5.9 source results in a SQLite which does not exhibit this particular bug.