Lines Matching refs:callback
357 ** The type for a callback function.
375 ** argument. ^If the callback function of the 3rd argument to
379 ** callback invocation. ^If the callback pointer to sqlite3_exec()
380 ** is NULL, then no callback is ever invoked and result rows are
395 ** ^If an sqlite3_exec() callback returns non-zero, the sqlite3_exec()
396 ** routine returns SQLITE_ABORT without invoking the callback again and
399 ** ^The 2nd argument to the sqlite3_exec() callback function is the
401 ** callback is an array of pointers to strings obtained as if from
404 ** sqlite3_exec() callback is a NULL pointer. ^The 4th argument to the
405 ** sqlite3_exec() callback is an array of pointers to strings where each
428 int (*callback)(void*,int,char**,char**), /* Callback function */
429 void *, /* 1st argument to callback */
1037 ** to the connection's busy-handler callback. The argument is of type (void**)
2024 ** The second should be of type (void*). The callback is invoked by the library
2557 ** program uses the [changes() SQL function], or if some other callback
2711 ** KEYWORDS: {busy-handler callback} {busy handler}
2714 ** ^The sqlite3_busy_handler(D,X,P) routine sets a callback function X
2722 ** ^If the busy callback is NULL, then [SQLITE_BUSY]
2723 ** is returned immediately upon encountering the lock. ^If the busy callback
2724 ** is not NULL, then the callback might be invoked with two arguments.
2728 ** the busy handler callback is the number of times that the busy handler has
2730 ** busy callback returns 0, then no additional attempts are made to
2733 ** ^If the callback returns non-zero, then another attempt
2752 ** ^The default busy callback is NULL.
2760 ** The busy callback should not take any actions which modify the
3055 ** KEYWORDS: {authorizer callback}
3057 ** ^This routine registers an authorizer callback with a particular
3059 ** ^The authorizer callback is invoked as SQL statements are being compiled
3064 ** to perform various actions, the authorizer callback is invoked to
3065 ** see if those actions are allowed. ^The authorizer callback should
3069 ** rejected with an error. ^If the authorizer callback returns
3074 ** When the callback returns [SQLITE_OK], that means the operation
3075 ** requested is ok. ^When the callback returns [SQLITE_DENY], the
3080 ** ^The first parameter to the authorizer callback is a copy of the third
3082 ** to the callback is an integer [SQLITE_COPY | action code] that specifies
3084 ** to the callback are either NULL pointers or zero-terminated strings
3087 ** of the third through the sixth parameters of the authorization callback.
3090 ** and the callback returns [SQLITE_IGNORE] then the
3098 ** "SELECT count(*) FROM tab") then the [SQLITE_READ] authorizer callback
3100 ** ^If the action code is [SQLITE_DELETE] and the callback returns
3122 ** previous call.)^ ^Disable the authorizer by installing a NULL callback.
3125 ** The authorizer callback must not do anything that will modify
3126 ** the database connection that invoked the authorizer callback.
3133 ** correct authorizer callback remains in place during the [sqlite3_step()].
3135 ** ^Note that the authorizer callback is invoked only during
3150 ** The [sqlite3_set_authorizer | authorizer callback function] must
3165 ** The [sqlite3_set_authorizer()] interface registers a callback function
3167 ** second parameter to the callback is an integer code that specifies
3169 ** the authorizer callback may be passed.
3173 ** callback function will be parameters or NULL depending on which of these
3175 ** authorizer callback is the name of the database ("main", "temp",
3176 ** etc.) if applicable.)^ ^The 6th parameter to the authorizer callback
3224 ** These routines register callback functions that can be used for
3227 ** ^The callback function registered by sqlite3_trace() is invoked at
3229 ** ^The sqlite3_trace() callback is invoked with a UTF-8 rendering of the
3238 ** ^The callback function registered by sqlite3_profile() is invoked
3239 ** as each SQL statement finishes. ^The profile callback contains
3241 ** of how long that statement took to run. ^The profile callback
3245 ** might provide greater resolution on the profiler callback. Invoking
3247 ** profile callback.
3261 ** the following constants. ^The first argument to the trace callback
3266 ** ^A trace callback has four arguments: xCallback(T,C,P,X).
3274 ** <dd>^An SQLITE_TRACE_STMT callback is invoked when a prepared statement
3280 ** that indicates the invocation of a trigger. ^The callback can compute
3286 ** <dd>^An SQLITE_TRACE_PROFILE callback provides approximately the same
3287 ** information as is provided by the [sqlite3_profile()] callback.
3291 ** ^The SQLITE_TRACE_PROFILE callback is invoked when the statement finishes.
3294 ** <dd>^An SQLITE_TRACE_ROW callback is invoked whenever a prepared
3300 ** <dd>^An SQLITE_TRACE_CLOSE callback is invoked when a database
3315 ** ^The sqlite3_trace_v2(D,M,X,P) interface registers a trace callback
3317 ** and context pointer P. ^If the X callback is
3325 ** ^The X callback is invoked whenever any of the events identified by
3326 ** mask M occur. ^The integer return value from the callback is currently
3330 ** ^A trace callback is invoked with four arguments: callback(T,C,P,X).
3332 ** constants to indicate why the callback was invoked.
3351 ** ^The sqlite3_progress_handler(D,N,X,P) interface causes the callback
3358 ** callback function X. ^The parameter N is the approximate number of
3360 ** invocations of the callback X. ^If N is less than one then the progress
3369 ** ^If the progress callback returns non-zero, the operation is
3373 ** The progress handler callback must not do anything that will modify
5206 ** created) and the presence or absence of a destructor callback for
5208 ** is similar, but allows the user to supply the extra callback functions
5274 ** callback only; NULL pointers must be passed as the xStep and xFinal
5295 ** sqlite3_create_function_v2() fails. ^When the destructor callback is
5664 ** called once for each invocation of the xStep callback and then one
5665 ** last time when the xFinal callback is invoked. ^(When no rows match
5666 ** an aggregate query, the xStep() callback of the aggregate function
5679 ** allocation.)^ Within the xFinal callback, it is customary to set
5688 ** to the xStep or xFinal callback routine that implements the aggregate
6009 ** to the collating function callback, xCompare.
6016 ** through as the first argument to the collating function callback.
6026 ** ^The collating function callback is invoked with a copy of the pArg
6029 ** function callback are the length of the two strings, in bytes. The collating
6051 ** with the addition that the xDestroy callback is invoked on pArg when
6057 ** ^The xDestroy callback is <u>not</u> called if the
6096 ** can be used, a single callback function may be registered with the
6104 ** ^A call to either function replaces the existing collation-needed callback.
6106 ** ^(When the callback is invoked, the first argument passed is a copy
6114 ** The callback function should register the desired collation using
6460 ** ^The sqlite3_commit_hook() interface registers a callback
6462 ** ^Any callback set by a previous call to sqlite3_commit_hook()
6464 ** ^The sqlite3_rollback_hook() interface registers a callback
6466 ** ^Any callback set by a previous call to sqlite3_rollback_hook()
6468 ** ^The pArg argument is passed through to the callback.
6469 ** ^If the callback on a commit hook function returns non-zero,
6478 ** The callback implementation must not do anything that will modify
6479 ** the database connection that invoked the callback. Any actions
6487 ** ^Registering a NULL function disables the callback.
6489 ** ^When the commit hook callback routine returns zero, the [COMMIT]
6498 ** ^The rollback callback is not invoked if a transaction is
6510 ** ^The sqlite3_autovacuum_pages(D,C,P,X) interface registers a callback
6512 ** file. ^The callback is passed a copy of the generic data pointer (P),
6515 ** and the number of bytes per page, respectively. The callback should
6517 ** autovacuum. ^If the callback returns zero, then no autovacuum happens.
6523 ** callback is invoked separately for each file.
6525 ** <p><b>The callback is not reentrant.</b> The callback function should
6528 ** files. The callback function should be a simple function that
6533 ** invoked whenever the database connection closes or when the callback
6536 ** <p>^There is only one autovacuum pages callback per database connection.
6538 ** previous invocations for that database connection. ^If the callback
6540 ** then the autovacuum steps callback is cancelled. The return value
6546 ** <p>If no autovacuum pages callback is specified (the usual case) or
6547 ** a NULL pointer is provided for the callback,
6549 ** words, the default behavior is the same as if the callback function
6576 ** ^The sqlite3_update_hook() interface registers a callback function
6580 ** ^Any callback set by a previous call to this function
6585 ** ^The first argument to the callback is a copy of the third argument
6587 ** ^The second callback argument is one of [SQLITE_INSERT], [SQLITE_DELETE],
6588 ** or [SQLITE_UPDATE], depending on the operation that caused the callback
6590 ** ^The third and fourth arguments to the callback contain pointers to the
6592 ** ^The final callback parameter is the [rowid] of the row.
9068 ** ^This API may be used to register a callback that SQLite will invoke
9084 ** the first argument to register for a callback that will be invoked
9086 ** callback is invoked from within the [sqlite3_step] or [sqlite3_close]
9092 ** If this happens, then the specified callback is invoked immediately,
9100 ** ^(There may be at most one unlock-notify callback registered by a
9102 ** blocked connection already has a registered unlock-notify callback,
9103 ** then the new callback replaces the old.)^ ^If sqlite3_unlock_notify() is
9105 ** unlock-notify callback is canceled. ^The blocked connections
9106 ** unlock-notify callback may also be canceled by closing the blocked
9109 ** The unlock-notify callback is not reentrant. If an application invokes
9110 ** any sqlite3_xxx API functions from within an unlock-notify callback, a
9118 ** When an unlock-notify callback is registered, the application provides a
9119 ** single void* pointer that is passed to the callback when it is invoked.
9120 ** However, the signature of the callback function allows SQLite to pass
9122 ** an unlock-notify callback is a pointer to an array of void* pointers,
9127 ** callback. ^If two or more such blocked connections have specified the
9128 ** same callback function, then instead of invoking the callback function
9136 ** Assuming that after registering for an unlock-notify callback a
9137 ** database waits for the callback to be issued before taking any further
9147 ** unlock-notify callback is registered. The system is said to be in
9149 ** callback on the conclusion of connection B's transaction, and connection
9150 ** B has itself registered for an unlock-notify callback when connection
9153 ** registered for an unlock-notify callback on the conclusion of connection
9165 ** sqlite3_unlock_notify() results in the unlock-notify callback being
9260 ** ^The [sqlite3_wal_hook()] function is used to register a callback that
9263 ** ^(The callback is invoked by SQLite after the commit has taken place and
9267 ** ^The first parameter passed to the callback function when it is invoked
9269 ** registering the callback. ^The second is a copy of the database handle.
9275 ** The callback function should normally return [SQLITE_OK]. ^If an error
9277 ** SQLite code base to cause the statement that provoked the callback
9279 ** callback returns [SQLITE_ROW] or [SQLITE_DONE], or if it returns a value
9283 ** A single database handle may have at most a single write-ahead log callback
9285 ** previously registered write-ahead log callback. ^The return value is
9309 ** ^The callback registered by this function replaces any existing callback
9310 ** registered using [sqlite3_wal_hook()]. ^Likewise, registering a callback
9345 ** start a callback but which do not need the full power (and corresponding
9363 ** in the log were checkpointed. ^The [busy-handler callback]
9370 ** [sqlite3_busy_handler|busy-handler callback]) until there is no
9379 ** [busy-handler callback])
9520 ** silently replace the appropriate rows within the xUpdate callback and
9869 ** return value from the [sqlite3_set_authorizer()] callback and that
9873 /* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback */
9996 ** immediately and there is a busy-handler callback configured, it is invoked
10021 ** ^The [sqlite3_preupdate_hook()] interface registers a callback function
10036 ** ^The second parameter to the preupdate callback is a pointer to
10038 ** ^The third parameter to the preupdate callback is one of the constants
10041 ** ^(The fourth parameter to the preupdate callback is the name of the
10046 ** ^The fifth parameter to the preupdate callback is the name of the
10050 ** parameter passed to the preupdate callback is the initial [rowid] of the
10055 ** or updated. The value of the seventh parameter passed to the callback
10062 ** may only be called from within a preupdate callback. Invoking any of
10063 ** these routines from outside of a preupdate callback or with a
10065 ** to the preupdate callback results in undefined and probably undesirable
10076 ** preupdate callbacks; if it is used by an SQLITE_INSERT callback then the
10078 ** will be destroyed when the preupdate callback returns.
10085 ** preupdate callbacks; if it is used by an SQLITE_DELETE callback then the
10087 ** will be destroyed when the preupdate callback returns.
10090 ** callback was invoked as a result of a direct insert, update, or delete
10098 ** callback made with op==SQLITE_DELETE is actuall a write using the