Edit: HOWEVER, just ran an integrity check, and that did fail. "wrong # of entries in index sqlite_autoindex_t1_1"
On Thu, May 9, 2019 at 3:52 PM Chris Locke <[email protected]> wrote: > Are you using a new database when you create your table, or using an > existing database? > Are you writing your database locally? > What operating system / sqlite version are you using? > > The above test works for me... > > > Execution finished without errors. > > > Result: 1 rows returned in 62ms > > > At line 4: > > > SELECT DISTINCT * FROM t1 WHERE (t1.c0 IS NULL); > > > > > On Thu, May 9, 2019 at 3:47 PM Manuel Rigger <[email protected]> > wrote: > >> Hi, >> >> I discovered a sequence of statements that results in a malformed database >> disk image: >> >> CREATE TABLE t1 (c0, c1 REAL PRIMARY KEY); >> INSERT INTO t1(c0, c1) VALUES (TRUE, 9223372036854775807), (TRUE, 0); >> UPDATE t1 SET c0 = NULL; >> UPDATE OR REPLACE t1 SET c1 = 1; >> SELECT DISTINCT * FROM t1 WHERE (t1.c0 IS NULL); >> >> The last statement returns the following: >> |1.0 >> Error: near line 5: database disk image is malformed >> >> Unlike some of my previous test cases, this actually looks like something >> that could happen in practice, or what do you think? >> >> Best, >> Manuel >> _______________________________________________ >> sqlite-users mailing list >> [email protected] >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
