On Mon, Feb 10, 2014 at 9:02 PM, Richard Hipp <d...@sqlite.org> wrote:
>
> Your work-arounds pending the patch release:
>
> (1) Do not compile with SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4
> (2) Change your query so that it says "+moved_to IS NOT NULL" - add a
> unary "+" operator before every column name that is subject to an IS NOT
> NULL operator.
>
A third work-around:
(3) After opening each database connection ("db") run the following code:
if( strcmp(sqlite3_sourceid(),"2013-08-26 23:00")>0
&& strcmp(sqlite3_sourceid(),"2014-02-11")<0 ){
sqlite3_test_control(SQLITE_TESTCTRL_OPTIMIZATIONS, db, 0x800);
}
The call to sqlite3_test_control() will disable the STAT3 and STAT4 logic,
which will suppress the bug.
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
