there is a RETURNING clause, since that optimization is not able to deal
with RETURNING. See [forum:/forumpost/595e132f71|forum thread 595e132f71]
for details.
FossilOrigin-Name: 1d3760a517b8bd2a6be82d2d5788945f49397cdc539fe28fd23e2c0c62a1dbe2
SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option to sqlite3_db_config().
Fix for ticket [6484e6ce678fffab]
FossilOrigin-Name: 4d424f3047b48fc441475137f30a719d2f079390c86fe2617710ddfb05c5e240
optimization for subsequent VACUUM operations on tables with one or more CHECK
constraints. This could result in VACUUM producing slightly larger database
files.
FossilOrigin-Name: e5bb7db51cdfd8124c60329782798cea398733545594dab55cb892b2a08c4d29
generates output directly in the registers that INSERT INTO will be using,
in many cases, and OP_SCopy operations can thus be avoided.
FossilOrigin-Name: aa2d8b0e8154dd2f5e2c837dc11ab362b083495b
of "$TYPE constraint failed: $DETAIL". This involves many changes to the
expected output of test cases.
FossilOrigin-Name: 54b221929744b1bcdbcc2030fef2e510618afd41
with INTEGER PRIMARY KEY ON CONFLICT ... as long as the destination table
is initially empty. Improvements to the comments on the xfer optimization.
New test cases added.
FossilOrigin-Name: e3f368cd5ef66a56fd4bd05a77276039e26b9e0e
the destination table contains an INTEGER PRIMARY KEY ON CONFLICT... column.
Ticket [676bc02b87176125].
FossilOrigin-Name: 6f9898db7ff0730cc03f561f9c32ef3dee7e5d81
any foreign key constraint and foreign key constraints are enabled.
Ticket [6284df89debdf].
FossilOrigin-Name: ddeea5ab5f6c0c4a86cdfbbb9f24d9d54bf8d301
we really need to write more tests for the xfer optimization in order to
look for other related problems before closing this ticket. (CVS 3835)
FossilOrigin-Name: 34fec312fd1aeabb04e07d6aa061991775c7b8a1
