Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||Document the fact that UPSERTs count INSERT operations but not UPDATEs.|
|Timelines:||family | ancestors | descendants | both | trunk|
|Files:||files | file ages | folders|
|User & Date:||drh 2018-04-20 00:00:28|
|00:02||Updates to the change log. check-in: 6d211fe371 user: drh tags: trunk|
|00:00||Document the fact that UPSERTs count INSERT operations but not UPDATEs. check-in: fcfd6e8be6 user: drh tags: trunk|
|13:28||Preliminary documentation for upsert. check-in: 74564b6da7 user: drh tags: trunk|
Changes to pages/pragma.in.
446 446 447 447 <p>Query or change the count-changes flag. Normally, when the 448 448 count-changes flag is not set, [INSERT], [UPDATE] and [DELETE] statements 449 449 return no data. When count-changes is set, each of these commands 450 450 returns a single row of data consisting of one integer value - the 451 451 number of rows inserted, modified or deleted by the command. The 452 452 returned change count does not include any insertions, modifications 453 - or deletions performed by triggers, or any changes made automatically 454 - by [foreign key actions].</p> 453 + or deletions performed by triggers, any changes made automatically 454 + by [foreign key actions], or updates caused by an [upsert].</p> 455 455 456 456 <p>Another way to get the row change counts is to use the 457 457 [sqlite3_changes()] or [sqlite3_total_changes()] interfaces. 458 458 There is a subtle different, though. When an INSERT, UPDATE, or 459 459 DELETE is run against a view using an [INSTEAD OF trigger], 460 460 the count_changes pragma reports the number of rows in the view 461 461 that fired the trigger, whereas [sqlite3_changes()] and