sqlite/test/tkt2391.test
danielk1977 bcbb04e501 Consider explicit collate clauses when matching WHERE constraints to indices. Fix for #2391. (CVS 4040)
FossilOrigin-Name: f9a95e92dfaaa61ec0a44b9b7017b07929c94d26
2007-05-29 12:11:29 +00:00

50 lines
1.3 KiB
Plaintext

#
# 2007 May 28
#
# The author disclaims copyright to this source code. In place of
# a legal notice, here is a blessing:
#
# May you do good and not evil.
# May you find forgiveness for yourself and forgive others.
# May you share freely, never taking more than you give.
#
#***********************************************************************
# $Id: tkt2391.test,v 1.1 2007/05/29 12:11:30 danielk1977 Exp $
set testdir [file dirname $argv0]
source $testdir/tester.tcl
do_test tkt2391.1 {
execsql {
CREATE TABLE folders(folderid, parentid, foldername COLLATE binary);
INSERT INTO folders VALUES(1, 3, 'FolderA');
INSERT INTO folders VALUES(1, 3, 'folderB');
INSERT INTO folders VALUES(4, 0, 'FolderC');
}
} {}
do_test tkt2391.2 {
execsql {
SELECT count(*) FROM folders WHERE foldername < 'FolderC';
}
} {1}
do_test tkt2391.3 {
execsql {
SELECT count(*) FROM folders WHERE foldername < 'FolderC' COLLATE nocase;
}
} {2}
# This demonstrates the bug. Creating the index causes SQLite to ignore
# the "COLLATE nocase" clause and use the default collation sequence
# for column "foldername" instead (happens to be BINARY in this case).
#
do_test tkt2391.4 {
execsql {
CREATE INDEX f_i ON folders(foldername);
SELECT count(*) FROM folders WHERE foldername < 'FolderC' COLLATE nocase;
}
} {2}
finish_test