Lines Matching refs:update
6954 ** ^In the case of an update, this is the [rowid] after the update takes place.
6956 ** ^(The update hook is not invoked when internal system tables are
6958 ** ^The update hook is not invoked when [WITHOUT ROWID] tables are modified.
6960 ** ^In the current implementation, the update hook
6962 ** [ON CONFLICT | ON CONFLICT REPLACE] clause. ^Nor is the update hook
6967 ** The update hook implementation must not do anything that will modify
6968 ** the database connection that invoked the update hook. Any actions
6970 ** completion of the [sqlite3_step()] call that triggered the update hook.
7512 ** part of the same statement to delete or update a virtual table row and the
10397 ** CAPI3REF: The pre-update hook.
10422 ** kind of update operation that is about to occur.
10472 ** callback was invoked as a result of a direct insert, update, or delete
10477 ** When the [sqlite3_blob_write()] API is used to update a blob column,
10478 ** the pre-update hook is invoked with SQLITE_DELETE. This is because the
10483 ** pre-update hook is being invoked for some other reason, including a
11019 ** is not possible for an application to register a pre-update hook on a
11022 ** which a pre-update hook is already defined. The results of attempting
11293 ** <li> For each record generated by an update or delete, the database is
11370 ** used to update the table in database zFrom (call this the "from-table")
11652 ** is similar to the "old.*" columns available to update or delete triggers.
11685 ** this is similar to the "new.*" columns available to update or delete
12008 ** update the "main" database attached to handle db with the changes found in
12229 ** (non primary-key) fields modified by the update do not contain the
12326 ** Rebasing a changeset is to update it to take those conflict
12361 ** with a DELETE, and the conflict resolution was OMIT, then the update
12363 ** from the update change are filled in using the old.* values from
17087 PreUpdate *pPreUpdate; /* Context for active pre-update callback */
17179 #define SQLITE_WriteSchema 0x00000001 /* OK to update SQLITE_SCHEMA */
17930 ** update can proceed. Processing continues and no error is reported.
19273 #define OPFLAG_NCHANGE 0x01 /* OP_Insert: Set to update db->nChange */
19277 #define OPFLAG_LASTROWID 0x20 /* Set to update db->lastRowid */
19281 #define OPFLAG_ISNOOP 0x40 /* OP_Delete does pre-update-hook only */
19363 ** zTarget -> Dequoted name of the table to update.
19366 ** pExprList -> A list of the columns to update and the expressions to update
20230 #define ONEPASS_SINGLE 1 /* ONEPASS valid for a single row update */
22874 bft changeCntOn:1; /* True to update the change-counter */
34145 /* adjust exponent by d, and update sign */
39118 /* Always update the timestamp on the old file */
39172 /* To downgrade to shared, simply update our internal notion of the
41919 ** also update the in-memory values. */
44370 /* update conch with host and path (this will fail if other process
55150 ** Use as many entries from the input list as required and update the
55536 ** transaction other than the update of the transaction sequence
55984 ** need only update the change-counter once, for the first transaction
56962 ** since the most recent journal header was written, update the
57860 ** page in the pager cache. In this case just update the pager cache,
57870 ** If in WRITER_DBMOD, WRITER_FINISHED or OPEN state, then we update the
58470 ** update the change-counter at all. This may lead to cache inconsistency
58590 ** This is an unconditional update. See also the pager_incr_changecounter()
58591 ** routine which only updates the change-counter if the update is actually
59778 ** <update nRec field>
59985 /* If page 1 was just written, update Pager.dbFileVers to match
59987 ** page caused the database file to grow, update dbFileSize.
61809 ** To avoid excess churning of page 1, the update only happens once.
61811 ** unconditional update of the change counters.
61869 /* Actually do the update of the change counter */
62042 ** does this depends on whether or not the atomic-update optimization
62052 ** pager_incr_changecounter() function is called to update the change
62056 ** pager_incr_changecounter() to update the change-counter in indirect
62060 ** then call pager_incr_changecounter() to update the change-counter
62109 ** If the atomic-update optimization is being used, this sync will not
62113 ** atomic-update optimization is used it is almost certain that the
65567 ** file-system. To avoid this, update the wal-index header to
66071 ** update values of the aReadMark[] array in the header, but if it does
66827 ** In theory it would be Ok to update the cache of the header only
67202 /* If this is a commit, update the wal-index header too. */
72209 ** file is not pBt->pageSize. In this case lockBtree() will update
72267 ** client has been writing the database file), update it now. Doing
76306 /* If this is an auto-vacuum database, update the pointer map
76450 /* If this is an auto-vacuum database, update the pointer-map entries
77134 /* Now update the actual sibling pages. The order in which they are updated
77139 ** then it is not safe to update page apNew[iPg] until after
77143 ** then it is not safe to update page apNew[iPg] until after
77146 ** If neither of the above apply, the page is safe to update.
77167 /* Verify condition (1): If cells are moving left, update iPg
77171 /* Verify condition (2): If cells are moving right, update iPg
79976 int bUpdate /* True for an update, false otherwise */
83361 /* NOTE: Be sure to update mkopcodeh.tcl when adding or removing
85845 ** has been rolled back, update the database connection change-counter.
87630 ** Set a flag in the vdbe to update the change counter when it is finalised
87792 ** Invoke the pre-update hook. If this is an UPDATE or DELETE pre-update call,
87794 ** to be update or deleted. If the application calls sqlite3_preupdate_old(),
87798 Vdbe *v, /* Vdbe pre-update hook is invoked by */
89827 ** This function is called from within a pre-update callback to retrieve
89836 ** SQLITE_UPDATE pre-update callback, and that iIdx is within range. */
89891 ** This function is called from within a pre-update callback to retrieve
89902 ** This function is designed to be called from within a pre-update callback
89920 ** This function is designed to be called from within a pre-update callback
89931 ** This function is called from within a pre-update callback to retrieve
90360 ** This macro evaluates to true if either the update hook or the preupdate
91369 /* Most jump operations do a goto to this spot in order to update
95882 ** the update hook.
95885 ** not NULL, then the update-hook (sqlite3.xUpdateCallback) is invoked
95902 const char *zDb; /* database name - used by the update hook */
95903 Table *pTab; /* Table structure - used by update and pre-update hooks */
95936 /* Invoke the pre-update hook, if any */
95942 /* Prevent post-update hook from running in cases when it should not */
95968 /* Invoke the update-hook if required. */
96032 ** the update or pre-update hook, or both, may be invoked. The P1 cursor must
96034 ** this case. Specifically, if one is configured, the pre-update hook is
96035 ** invoked if P4 is not NULL. The update-hook is invoked if one is configured,
96040 ** be set to by the update.
96071 /* If the update-hook or pre-update-hook will be invoked, set zDb to
96090 /* Invoke the pre-update-hook if required. */
96130 /* Invoke the update-hook if required. */
98645 ** apply in the case of a constraint failure on an insert or update.
99669 /* If a pre-update hook is registered and this is a write cursor,
101430 ** set aTree[i] to its index and update pReadr1. If vdbeSorterCompare()
112413 ** not true, similarly update all SQL statements in the sqlite_schema table
112569 /* If the sqlite_sequence table exists in this database, then update
114087 ** expressions. Also update the name that appears right after the
120348 ** schema table. We just need to update that slot with all
120382 /* Reparse everything to update our internal data structures */
120747 ** Code to update the sqlite_schema tables and internal schema definitions
124525 ** invoke the update-hook. The pre-update-hook, on the other hand should
124527 ** the update-hook is not invoked for rows removed by REPLACE, but the
124528 ** pre-update-hook is.
127926 int bChngRowid /* True if rowid is modified by this update */
128211 ** This function is called before generating code to update or delete a
128241 ** This function is called before generating code to update or delete a
128539 ** for this operation (either update or delete), invoke the associated
128986 ** update the AUTOINCREMENT counters during a VACUUM.)
130182 ** the data to be inserted or the data after the update. There will be
130249 ** any IGNORE The attempt in insert or update the current
130718 /* This OP_Delete opcode fires the pre-update-hook only. It does
130797 ** the insert or update. Store that record in the aRegIdx[ix] register
130866 ** must be explicitly deleted in order to ensure any pre-update hook
130921 ** KEY values of this row before the update. */
131122 ** PK index. This function adds code to invoke the pre-update hook,
133566 ** ../tool/mkpragmatab.tcl. To update the set of pragmas, edit
142243 ** Expression walker callback used by renumberCursors() to update
147840 /************** Begin file update.c ******************************************/
148199 /* Locate the table which we want to update.
148451 ** two-pass update algorithm. */
148471 /* If we are trying to update a view, realize that view into
148568 ** Do not consider a single-pass strategy for a multi-row update if
148580 /* A one-pass strategy that might update more than one row may not
148662 /* Top of the update loop */
148835 ** all columns not modified by the update statement into their registers
148896 ** to invoke the pre-update hook.
148899 ** pre-update hook. If the caller invokes preupdate_new(), the returned
149190 /************** End of update.c **********************************************/
150416 ** schema table. We just need to update that slot with all
151217 ** table update operation currently in progress.
163777 ** search list pList for a matching WINDOW definition, and update pWin
163788 Window *pWin, /* Window frame to update */
178933 ** To amortize update costs, segments are grouped into levels and
178983 ** index into the term index, we clearly cannot simply update the term
189901 ** this file contains code to insert, update and delete rows from FTS3
193636 ** unmodified. Otherwise, if the allocation succeeds, update pBlob->nAlloc
200402 ** sure to update the xBestIndex method. */
203667 ** This operation is required when a row is deleted (or updated - an update
203799 ** number of cells, remove it from the tree. Otherwise, update the
208188 ** The RBU extension requires that the RBU update be packaged as an
208193 ** update, insert or delete from the target table.
208195 ** The update proceeds in three stages:
208204 ** During this stage RBU does not update the database by writing
208207 ** to update each b-tree individually. All updates required by each
208219 ** the updates made as part of the RBU update.
208235 ** the RBU update database are not atomic. So if the power fails at the
208237 ** committed before the RBU update database this will likely either just
208241 ** If some client does modify the target database mid RBU update, or some
208244 ** by delete the RBU update database and *-oal file and have the device
208245 ** download the update again and start over.
208250 ** data to disk when saving the state of an ongoing update to the RBU
208251 ** update database than is strictly necessary.
208286 ** The problem is that in order to update a b-tree, the leaf page (at least)
208306 ** guarantee that a single update process will run for long enough to apply
208307 ** the entire update, for example because the update is being applied on a
208313 ** "RBU" stands for "Resumable Bulk Update". As in a large database update
208315 ** applied using this extension is hence refered to as an "RBU update".
208320 ** An "RBU update" transaction is subject to the following limitations:
208345 ** An "RBU update" is stored as a separate SQLite database. A database
208346 ** containing an RBU update is an "RBU database". For each table in the
208403 ** update, the corresponding data_% table should contain a single record
208413 ** update, the corresponding data_% table should contain a single record
208420 ** update, the corresponding data_% table should contain a single record
208422 ** The real primary key values identifying the row to update should be
208424 ** the new values of all columns being update. The text value in the
208431 ** above, the update statement:
208483 ** The API declared below allows an application to apply an RBU update
208496 ** a complete update.
208498 ** 4) Calls sqlite3rbu_close() to close the RBU update handle. If
208500 ** apply the update to the target database, then the RBU database
208502 ** update application is saved in the RBU database for later
208507 ** If an update is only partially applied to the target database by the
208510 ** resume the RBU update from where it left off.
208518 ** An RBU update may not be applied to a database in WAL mode. Attempting
208525 ** If an RBU update is started and then suspended before it is completed,
208527 ** the suspended RBU update is also an error (SQLITE_BUSY).
208552 ** the current state of the update (how many rows have been updated, which
208555 ** organize removing a separate state file after the update is concluded.
208557 ** the RBU extension can store the state of the update.
208559 ** When resuming an RBU update, the zState argument must be passed the same
208560 ** value as when the RBU update was started.
208562 ** Once the RBU update is finished, the RBU extension does not
208583 ** that it can be suspended and resumed like an RBU update.
208646 ** connection to access the target and rbu update databases. This
208651 ** database handle, or non-zero to access the rbu update database handle.
208661 ** the rbu update db handle to any required virtual table
208678 ** Do some work towards applying the RBU update to the target db.
208680 ** Return SQLITE_DONE if the update has been completely applied, or
208682 ** the RBU update. If an error does occur, some other error code is
208694 ** If a power failure or application crash occurs during an update, following
208695 ** system recovery RBU may resume the update from the point at which the state
208706 ** If the RBU update has been completely applied, mark the RBU database
208708 ** current state of the RBU update appliation to the RBU database.
208718 ** update has been partially applied, or SQLITE_DONE if it has been
208726 ** current RBU update was started.
208732 ** progress indications for the two stages of an RBU update. This API may
208735 ** An RBU update is divided into two stages:
208741 ** The update is visible to non-RBU clients during stage 2. During stage 1
208744 ** If this API is called during stage 2 of the update, output variable
208750 ** If this API is called during stage 1 of the update, output variable
208773 ** Obtain an indication as to the current stage of an RBU update or vacuum.
208785 ** operation is an RBU update, then the updated version of the database
208811 ** As part of applying an RBU update or performing an RBU vacuum operation,
208931 ** update so that it can be resumed later. The table consists of integer
208940 ** 5: the rbu update has been checkpointed.
208957 ** rbu update.
209041 char *zMask; /* Copy of update mask used with pUpdate */
209042 sqlite3_stmt *pUpdate; /* Last update statement (or NULL) */
209167 ** This estimate is accurate if the RBU update consists entirely of
209170 ** * the RBU update contains any UPDATE operations. If the PK specified
209176 ** * the RBU update contains any DELETE operations for which the specified
209180 ** * the RBU update contains REPLACE operations. These are similar to
209185 ** stored in the rbu_state table if the RBU update is suspended.
210375 ** rows from the sourct table, just as it does for an RBU update operation.
210695 ** an UPDATE statement used to update the table object that the iterator
211123 ** Ensure that the SQLite statement handles required to update the
211387 ** be used to update the imposter table for the main table b-tree of the
211391 ** If the zMask string does not specify any columns to update, then this
212088 ** point to the text value indicating the columns to update.
212598 ** an rbu handle in OAL stage. If the rbu update has not started (i.e.
212848 p->zErrmsg = sqlite3_mprintf("cannot update wal mode database");
212867 (rbuIsVacuum(p) ? "vacuum" : "update")
212883 ** update finished. */
213079 ** current RBU update was started.
213087 ** an RBU update.
213122 ** Return the current state of the RBU vacuum or update operation.
213251 ** object can be marked as the target database of an RBU update. This
213953 ** database connection exists, and the RBU update is in RBU_STAGE_OAL,
213957 ** ensures that the RBU extension never tries to update a database
215118 ** update fails. Rows may not be deleted or inserted.
215706 ** old.* record: (delete and update only)
215707 ** new.* record: (insert and update only)
215762 ** PRIMARY KEY fields contain the values identifying the table row to update,
216020 ** This function may only be called from within a pre-update callback.
216356 ** This function is only called from within a pre-update-hook callback.
216357 ** It determines if the current pre-update-hook change affects the same row
216359 ** if the pre-update-hook does not affect the same row as pChange, it returns
216366 int op /* Current pre-update operation */
216629 ** This function is only called from within a pre-update handler for a
216808 ** This function is only called from with a pre-update-hook reporting a
217002 ** The 'pre-update' hook registered by this module with SQLite databases.
217040 ** The pre-update hook implementations.
217056 ** Install the pre-update hooks on the session object passed as the only
217729 ** This function appends an update change to the buffer (see the comments
217730 ** under "CHANGESET FORMAT" at the top of the file). An update change
219171 /* Read the old.* and new.* records for the update change. */
219899 ** one is encountered, update or delete the row with the matching primary key
225632 ** Parse a "special" CREATE VIRTUAL TABLE directive and update
225642 Fts5Config *pConfig, /* Configuration object to update */
227143 ** to a value laster than *piLast, update *piLast to the new lastest value.
232837 Fts5Iter *pIter, /* Iterator to update aFirst[] array for */
232856 ** attempts to update the contents of the pIter->aFirst[] accordingly.
232864 Fts5Iter *pIter, /* Iterator to update aFirst[] array for */
234573 ** segment on disk. Also update the corresponding structure record.