1
0
mirror of https://github.com/sqlite/sqlite.git synced 2026-10-23 21:49:02 +03:00
Files
drh 245d21fb37 Only enforce the limit on the number of CTE cursors at
SQLITE_LIMIT_EXPR_DEPTH if SQLITE_DBCONFIG_DEFENSIVE is engaged.
Also give a different error message when the number of CTEs
grow too large.
This is a proposed work-around for the problem described at
[forum:/info/2026-10-16T20:30:17Z|Forum post 2026-10-16T20:30:17Z].
It does require the user to disable defensive.  Perhaps for 3.55.0
I should add a new limit instead, like SQLITE_LIMIT_CTES.

FossilOrigin-Name: 2161aefeb89842ba1675f469770b81b0c9946ebdfdcbca130440e81732463916
2026-10-18 00:34:48 +00:00
..
…
2025-03-27 14:37:07 +00:00
2025-07-15 18:51:46 +00:00
…
…
2026-07-20 16:45:50 +00:00
…
…
2023-10-12 18:09:27 +00:00
…
…
…
2026-07-24 00:39:41 +00:00
…
…
…
…
…
…
2026-07-24 00:39:41 +00:00
2024-03-06 20:38:52 +00:00
2023-06-15 15:43:08 +00:00
…
2026-07-24 00:39:41 +00:00
…
…
…
2025-11-05 22:33:47 +00:00
2025-12-02 18:37:49 +00:00
…
2023-07-01 17:56:00 +00:00
…
…
…
2026-07-24 00:39:41 +00:00
…
…
…
…
…
…
…