Is SQLITE_MAX_EXPR_DEPTH=0 still a recommended compiler option?
According to https://www.sqlite.org/draft/compile.html
SQLITE_MAX_EXPR_DEPTH=0. Setting the maximum expression parse-tree depth
to
zero disables all checking of the expression parse-tree depth, which
simplifies the code resulting in faster execution, and helps the parse
tree
to use less memory.
But, in the "sqliteLimit.h" header file comments for version 3.30.1,
/*
** The maximum depth of an expression tree. This is limited to
** some extent by SQLITE_MAX_SQL_LENGTH. But sometime you might
** want to place more severe limits on the complexity of an
** expression.
**
** A value of 0 used to mean that the limit was not enforced.
** But that is no longer true. The limit is now strictly enforced
** at all times.
*/
#ifndef SQLITE_MAX_EXPR_DEPTH
# define SQLITE_MAX_EXPR_DEPTH 1000
#endif
it seems to be at odds with the html documentation at first glance.
--
Sent from: http://sqlite.1065341.n5.nabble.com/
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
