Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Do not require a statement journal in cases where REPLACE conflict handling is used to insert a single row, so long as the REPLACE operation cannot fire any triggers or foreign key actions. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
469a62ca33081854e54f3af6d93ab5a3 |
| User & Date: | dan 2018-05-28 18:29:46.779 |
References
|
2019-12-15
| ||
| 02:49 | Ensure that all ON CONFLICT REPLACE indexes are sorted to the end of the list of indexes for a table, even for weird cases where the same UNIQUE constraint occurs twice with the ON CONFLICT REPLACE clause only on the second one. This avoids an out-of-order contraint processing problem that can arise due to the optimization of check-in [469a62ca33081854]. (check-in: 1e3918ca2f user: drh tags: trunk) | |
Context
|
2018-05-29
| ||
| 13:25 | Do not run test file "resetdb.test" as part of permutation "inmemory_journal". (check-in: 4921e5bae4 user: dan tags: trunk) | |
|
2018-05-28
| ||
| 18:29 | Do not require a statement journal in cases where REPLACE conflict handling is used to insert a single row, so long as the REPLACE operation cannot fire any triggers or foreign key actions. (check-in: 469a62ca33 user: dan tags: trunk) | |
| 18:25 | When compiling with SQLITE_DEBUG, add run-time checks to ensure that no statement aborts unless either there have been no writes or else there is a statement journal. (check-in: ce99c77244 user: drh tags: trunk) | |
Changes
Changes to src/insert.c.