I can confirm that the crash problem has been fixed by
http://www.sqlite.org/src/info/1258875e07 checked-in .
Now executing following sql will report no such collation sequence: RMNOCASE
instead of crash.
SELECT
Surname || ', ' || Given COLLATE NOCASE AS Person ,
Adr.Name COLLATE NOCASE AS
I hava a table. The table schema is
CREATE TABLE AddressTable
(
AddressID INTEGER PRIMARY KEY ,
AddressType INTEGER ,
Name TEXT COLLATE RMNOCASE ,
Street1 TEXT ,
Street2 TEXT ,
City TEXT ,
State TEXT ,
Zip TEXT ,
Country TEXT ,
Phone1 TEXT ,
Phone2 TEXT ,
Fax TEXT ,
*I just checked the **explain result of **sql below under 3.6.17 and
3.6.22, the result is quite different.
SQL:
-- romermb's incredible combination of events, shared events plus 'marriage'
and alternate names as Facts 2010-01-06
-- revised by ve3meo to to bring out RoleName from RoleTableand
I think I found a performance regression bug of sqlite 3.6.1 8. A sql will
cost 1800 seconds to return the query result with sqlite 3.6.18 and with the
previous version it only cost about 170 seconds.
I just attach the sql can reproduce the bug under below. But the database is
a little large
4 matches
Mail list logo
