> For example, if a table has multiple columns with UNIQUE indexes. But in my case, the table doesn't have any UNIQUE indexes, so it seems that the REPLACE statement can't affect more than one row. This is something that sqlite3GenerateConstraintChecks could check.
> The fact that the situation goes away when you get rid of the second NOT NULL > is interesting. I think the situation goes away when I get rid of the NOT NULL because then the statement can't be aborted. Jeremy _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
