On Tue, Jun 11, 2013 at 9:10 AM, <thomas.de...@panalytical.com> wrote:
> Hello, > > we just updated the SQLite sources/DLL in our project from version > 3.7.15.2 to version 3.7.17. > After executing the update we got a failing unit test concerning a string > based database search > with a very long string (but this string is present in our current SQLite > DB). In fact the reason of > the failing test/problem is the limitation of constant MAX_EXPR_DEPTH to > 12 in call "sqlite3Fts3ExprParse". > After changing this constant to 60 and a recompile the unit test didn't > fail anymore. > > The question is why is this constant set to such a small value and what is > the drawback when > we set this constant to a (much) higher value? > There are test cases that require 1<<MAX_EXPR_DEPTH or more terms in the query expression. So the limit is kept to a reasonable value to facilitate testing. We are working to allow you to increase this limit at compile-time. > > best regards, > > Thomas > > > PANalytical > The Analytical X-ray Company > > The information contained in this message is confidential and may be > legally privileged. The message is intended solely for the addressee(s). > If you are not the intended recipient, you are hereby notified that any > use, dissemination, or reproduction is strictly prohibited and may be > unlawful. If you are not the intended recipient, please contact the sender > by return e-mail and destroy all copies of the original message. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
