Sorry, forgot to mention that our previous version of SQLite was 3.7.17 and we
did not experience the issue there...
Am 20.03.2014 um 12:26 schrieb Jens Miltner <j...@mac.com>:
> Hi,
>
> I ran into the following problem after updating the SQLite 3.8.4.1:
>
> When executing the following (rather basic) SELECT query in a debug build of
> sqlite3, this will cause an assertion to fire in whereLoopAddBtreeIndex()
> (sqlite3.c, line 13411):
>
> SELECT * FROM t1 WHERE(foo_id=5 AND name IN ('foo'));
>
> The database schema to reproduce is:
>
> CREATE TABLE t1 (id INTEGER PRIMARY KEY, foo_id INTEGER, name VARCHAR(36),
> phone VARCHAR(36));
> CREATE UNIQUE INDEX t1_udx ON t1(name, foo_id);
> CREATE INDEX t1_idx ON t1 (phone, foo_id);
>
>
> The assertion that fires is the following:
>
> assert( (pNew->wsFlags & WHERE_COLUMN_IN)==0 || iCol<0 );
>
>
> This is quite annoying, since it will terminate the app when we build our app
> with DEBUG enabled and a similar query is executed.
>
> Can you SQLite folks please have a look into this?
>
> Thanks,
> -jens
>
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
