SQLite

View Ticket
Login
Plaintext
2016-09-07
11:27
Fix a problem in internal function sqlite3OpenTableAndIndices causing an operand of an unrelated VM instruction to be overwritten. Fix for [ef360601]. (check-in: e5c30f22 user: drh tags: branch-3.14)
2016-08-26
12:01 • Fixed ticket [ef360601]: Incorrect affinity transformations on DELETE plus 5 other changes (artifact: 06aa3be5 user: drh)
12:00
Fix a problem in internal function sqlite3OpenTableAndIndices causing an operand of an unrelated VM instruction to be overwritten. Fix for [ef360601]. (check-in: 70901479 user: dan tags: trunk)
05:17 • New ticket [ef360601] Incorrect affinity transformations on DELETE. (artifact: 21b6b00b user: drh)
Ticket Hash: ef36060112a5059184965d3c9816caf0c5f3bace
Title: Incorrect affinity transformations on DELETE
Status: Fixed Type: Code_Defect
Severity: Severe Priority: Immediate
Subsystem: Unknown Resolution: Fixed
Last Modified: 2016-08-26 12:01:20
Version Found In: 3.14.1
User Comments:
drh added on 2016-08-26 05:17:58:

In the SQL below, the DELETE operation is a no-op. 

CREATE TABLE t1(a INT UNIQUE, b INT);
INSERT INTO t1(a,b) VALUES('1','2');
SELECT * FROM t1 WHERE a='1' AND b='2';
DELETE FROM t1 WHERE a='1' AND b='2';
SELECT * FROM t1;

Even the SELECT on the third line outputs the row, and the DELETE has the exact same WHERE clause, the DELETE does not delete the row.

Bisecting suggests that this problem was introduced by check-in [85c467041c9378ca] on 2016-01-30 for version 3.11.0.