|15:23||• Fixed ticket [7be932df]: Adverse interaction between .stats and .eqp in the CLI plus 5 other changes (artifact: 07775835 user: drh)|
|15:23||Avoid using a prepared statement for ".stats on" after it has been closed by the ".eqp full" logic. Fix for ticket [7be932dfa60a8a6b3b26bcf76]. (check-in: bb87c054 user: drh tags: trunk)|
|15:11||• New ticket [7be932df] Adverse interaction between .stats and .eqp in the CLI. (artifact: facdb8d3 user: drh)|
|Title:||Adverse interaction between .stats and .eqp in the CLI|
|Last Modified:||2018-06-07 15:23:52|
|Version Found In:||3.24.0|
drh added on 2018-06-07 15:11:38:
The following script causes a segfault in the CLI:
CREATE TABLE t1(a,b); INSERT INTO t1 VALUES(1,2),(99,100),(4,3); .eqp full .stats on SELECT * FROM t1;
This problem appears to be a case of using a prepared statement after it has been finalized. The problem was introduced by check-in [ae34edb7f4fa7b37] on 2018-03-20 and first appeared in the version 3.23.0 release.
To be clear: This is a problem with the command-line shell auxiliary program that uses SQLite. It is not a defect in SQLite itself.
This problem was discovered during internal testing and has not been reported in the wild.