On 11/23/2015 07:55, James K. Lowden wrote: > As a matter of fact, violation of UNIQUE & PK constraints is enforced > rather too strictly in SQLite. Any UPDATE statement that modifie more > than one row of a UNIQUE column can fail because two rows may > *transiently* have the same value. SQLite will fail the statement > even though the completed transactation leaves the constraint > unviolated.
It seems like it performs the checking on the level of individual field write, not SQL statements. I suggested earlier to have "CONSTRAINT LEVEL [WRITE|STATEMENT|TRANSACTION];" It seems they currently work on the level of field writes and transactions, and not on SQL statement level. Yuri
