Potential bug with compile-time option SQLITE_OMIT_AUTOVACUUM

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Potential bug with compile-time option SQLITE_OMIT_AUTOVACUUM

Bernard Schurdevin
Hi,

Building amalgamation sqlite3.c with option SQLITE_OMIT_AUTOVACUUM=1
leads to malformed database on following case :

Windows 7 x64, mingw64 5.4 : gcc -s -static -DSQLITE_OMIT_AUTOVACUUM=1
shell.c sqlite3.c -o sqlite3.exe

using CLI (compiled with SQLITE_OMIT_AUTOVACUUM=1) :

.open base.db
CREATE TABLE foo (num INTEGER PRIMARY KEY,comment TEXT COLLATE NOCASE)
WITHOUT ROWID;
PRAGMA integrity_check; ===============> ok
DROP TABLE foo;
Error: database disk image is malformed

CLI refuses to drop the table and don't corrupt database, but direct
usage of API (sqlite3_step) corrupt the database :
*** in database main ***
2nd reference to page ...

Best regards

_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users