1 2 #if !defined(__SQLITESESSION_H_) && defined(SQLITE_ENABLE_SESSION) 3 #define __SQLITESESSION_H_ 1 4 5 /* 6 ** Make sure we can call this stuff from C++. 7 */ 8 #ifdef __cplusplus 9 extern "C" { 10 #endif 11 12 #include "sqlite3.h" 13 14 /* 15 ** CAPI3REF: Session Object Handle 16 ** 17 ** An instance of this object is a [session] that can be used to 18 ** record changes to a database. 19 */ 20 typedef struct sqlite3_session sqlite3_session; 21 22 /* 23 ** CAPI3REF: Changeset Iterator Handle 24 ** 25 ** An instance of this object acts as a cursor for iterating 26 ** over the elements of a [changeset] or [patchset]. 27 */ 28 typedef struct sqlite3_changeset_iter sqlite3_changeset_iter; 29 30 /* 31 ** CAPI3REF: Create A New Session Object 32 ** CONSTRUCTOR: sqlite3_session 33 ** 34 ** Create a new session object attached to database handle db. If successful, 35 ** a pointer to the new object is written to *ppSession and SQLITE_OK is 36 ** returned. If an error occurs, *ppSession is set to NULL and an SQLite 37 ** error code (e.g. SQLITE_NOMEM) is returned. 38 ** 39 ** It is possible to create multiple session objects attached to a single 40 ** database handle. 41 ** 42 ** Session objects created using this function should be deleted using the 43 ** [sqlite3session_delete()] function before the database handle that they 44 ** are attached to is itself closed. If the database handle is closed before 45 ** the session object is deleted, then the results of calling any session 46 ** module function, including [sqlite3session_delete()] on the session object 47 ** are undefined. 48 ** 49 ** Because the session module uses the [sqlite3_preupdate_hook()] API, it 50 ** is not possible for an application to register a pre-update hook on a 51 ** database handle that has one or more session objects attached. Nor is 52 ** it possible to create a session object attached to a database handle for 53 ** which a pre-update hook is already defined. The results of attempting 54 ** either of these things are undefined. 55 ** 56 ** The session object will be used to create changesets for tables in 57 ** database zDb, where zDb is either "main", or "temp", or the name of an 58 ** attached database. It is not an error if database zDb is not attached 59 ** to the database when the session object is created. 60 */ 61 int sqlite3session_create( 62 sqlite3 *db, /* Database handle */ 63 const char *zDb, /* Name of db (e.g. "main") */ 64 sqlite3_session **ppSession /* OUT: New session object */ 65 ); 66 67 /* 68 ** CAPI3REF: Delete A Session Object 69 ** DESTRUCTOR: sqlite3_session 70 ** 71 ** Delete a session object previously allocated using 72 ** [sqlite3session_create()]. Once a session object has been deleted, the 73 ** results of attempting to use pSession with any other session module 74 ** function are undefined. 75 ** 76 ** Session objects must be deleted before the database handle to which they 77 ** are attached is closed. Refer to the documentation for 78 ** [sqlite3session_create()] for details. 79 */ 80 void sqlite3session_delete(sqlite3_session *pSession); 81 82 83 /* 84 ** CAPI3REF: Enable Or Disable A Session Object 85 ** METHOD: sqlite3_session 86 ** 87 ** Enable or disable the recording of changes by a session object. When 88 ** enabled, a session object records changes made to the database. When 89 ** disabled - it does not. A newly created session object is enabled. 90 ** Refer to the documentation for [sqlite3session_changeset()] for further 91 ** details regarding how enabling and disabling a session object affects 92 ** the eventual changesets. 93 ** 94 ** Passing zero to this function disables the session. Passing a value 95 ** greater than zero enables it. Passing a value less than zero is a 96 ** no-op, and may be used to query the current state of the session. 97 ** 98 ** The return value indicates the final state of the session object: 0 if 99 ** the session is disabled, or 1 if it is enabled. 100 */ 101 int sqlite3session_enable(sqlite3_session *pSession, int bEnable); 102 103 /* 104 ** CAPI3REF: Set Or Clear the Indirect Change Flag 105 ** METHOD: sqlite3_session 106 ** 107 ** Each change recorded by a session object is marked as either direct or 108 ** indirect. A change is marked as indirect if either: 109 ** 110 ** <ul> 111 ** <li> The session object "indirect" flag is set when the change is 112 ** made, or 113 ** <li> The change is made by an SQL trigger or foreign key action 114 ** instead of directly as a result of a users SQL statement. 115 ** </ul> 116 ** 117 ** If a single row is affected by more than one operation within a session, 118 ** then the change is considered indirect if all operations meet the criteria 119 ** for an indirect change above, or direct otherwise. 120 ** 121 ** This function is used to set, clear or query the session object indirect 122 ** flag. If the second argument passed to this function is zero, then the 123 ** indirect flag is cleared. If it is greater than zero, the indirect flag 124 ** is set. Passing a value less than zero does not modify the current value 125 ** of the indirect flag, and may be used to query the current state of the 126 ** indirect flag for the specified session object. 127 ** 128 ** The return value indicates the final state of the indirect flag: 0 if 129 ** it is clear, or 1 if it is set. 130 */ 131 int sqlite3session_indirect(sqlite3_session *pSession, int bIndirect); 132 133 /* 134 ** CAPI3REF: Attach A Table To A Session Object 135 ** METHOD: sqlite3_session 136 ** 137 ** If argument zTab is not NULL, then it is the name of a table to attach 138 ** to the session object passed as the first argument. All subsequent changes 139 ** made to the table while the session object is enabled will be recorded. See 140 ** documentation for [sqlite3session_changeset()] for further details. 141 ** 142 ** Or, if argument zTab is NULL, then changes are recorded for all tables 143 ** in the database. If additional tables are added to the database (by 144 ** executing "CREATE TABLE" statements) after this call is made, changes for 145 ** the new tables are also recorded. 146 ** 147 ** Changes can only be recorded for tables that have a PRIMARY KEY explicitly 148 ** defined as part of their CREATE TABLE statement. It does not matter if the 149 ** PRIMARY KEY is an "INTEGER PRIMARY KEY" (rowid alias) or not. The PRIMARY 150 ** KEY may consist of a single column, or may be a composite key. 151 ** 152 ** It is not an error if the named table does not exist in the database. Nor 153 ** is it an error if the named table does not have a PRIMARY KEY. However, 154 ** no changes will be recorded in either of these scenarios. 155 ** 156 ** Changes are not recorded for individual rows that have NULL values stored 157 ** in one or more of their PRIMARY KEY columns. 158 ** 159 ** SQLITE_OK is returned if the call completes without error. Or, if an error 160 ** occurs, an SQLite error code (e.g. SQLITE_NOMEM) is returned. 161 ** 162 ** <h3>Special sqlite_stat1 Handling</h3> 163 ** 164 ** As of SQLite version 3.22.0, the "sqlite_stat1" table is an exception to 165 ** some of the rules above. In SQLite, the schema of sqlite_stat1 is: 166 ** <pre> 167 ** CREATE TABLE sqlite_stat1(tbl,idx,stat) 168 ** </pre> 169 ** 170 ** Even though sqlite_stat1 does not have a PRIMARY KEY, changes are 171 ** recorded for it as if the PRIMARY KEY is (tbl,idx). Additionally, changes 172 ** are recorded for rows for which (idx IS NULL) is true. However, for such 173 ** rows a zero-length blob (SQL value X'') is stored in the changeset or 174 ** patchset instead of a NULL value. This allows such changesets to be 175 ** manipulated by legacy implementations of sqlite3changeset_invert(), 176 ** concat() and similar. 177 ** 178 ** The sqlite3changeset_apply() function automatically converts the 179 ** zero-length blob back to a NULL value when updating the sqlite_stat1 180 ** table. However, if the application calls sqlite3changeset_new(), 181 ** sqlite3changeset_old() or sqlite3changeset_conflict on a changeset 182 ** iterator directly (including on a changeset iterator passed to a 183 ** conflict-handler callback) then the X'' value is returned. The application 184 ** must translate X'' to NULL itself if required. 185 ** 186 ** Legacy (older than 3.22.0) versions of the sessions module cannot capture 187 ** changes made to the sqlite_stat1 table. Legacy versions of the 188 ** sqlite3changeset_apply() function silently ignore any modifications to the 189 ** sqlite_stat1 table that are part of a changeset or patchset. 190 */ 191 int sqlite3session_attach( 192 sqlite3_session *pSession, /* Session object */ 193 const char *zTab /* Table name */ 194 ); 195 196 /* 197 ** CAPI3REF: Set a table filter on a Session Object. 198 ** METHOD: sqlite3_session 199 ** 200 ** The second argument (xFilter) is the "filter callback". For changes to rows 201 ** in tables that are not attached to the Session object, the filter is called 202 ** to determine whether changes to the table's rows should be tracked or not. 203 ** If xFilter returns 0, changes is not tracked. Note that once a table is 204 ** attached, xFilter will not be called again. 205 */ 206 void sqlite3session_table_filter( 207 sqlite3_session *pSession, /* Session object */ 208 int(*xFilter)( 209 void *pCtx, /* Copy of third arg to _filter_table() */ 210 const char *zTab /* Table name */ 211 ), 212 void *pCtx /* First argument passed to xFilter */ 213 ); 214 215 /* 216 ** CAPI3REF: Generate A Changeset From A Session Object 217 ** METHOD: sqlite3_session 218 ** 219 ** Obtain a changeset containing changes to the tables attached to the 220 ** session object passed as the first argument. If successful, 221 ** set *ppChangeset to point to a buffer containing the changeset 222 ** and *pnChangeset to the size of the changeset in bytes before returning 223 ** SQLITE_OK. If an error occurs, set both *ppChangeset and *pnChangeset to 224 ** zero and return an SQLite error code. 225 ** 226 ** A changeset consists of zero or more INSERT, UPDATE and/or DELETE changes, 227 ** each representing a change to a single row of an attached table. An INSERT 228 ** change contains the values of each field of a new database row. A DELETE 229 ** contains the original values of each field of a deleted database row. An 230 ** UPDATE change contains the original values of each field of an updated 231 ** database row along with the updated values for each updated non-primary-key 232 ** column. It is not possible for an UPDATE change to represent a change that 233 ** modifies the values of primary key columns. If such a change is made, it 234 ** is represented in a changeset as a DELETE followed by an INSERT. 235 ** 236 ** Changes are not recorded for rows that have NULL values stored in one or 237 ** more of their PRIMARY KEY columns. If such a row is inserted or deleted, 238 ** no corresponding change is present in the changesets returned by this 239 ** function. If an existing row with one or more NULL values stored in 240 ** PRIMARY KEY columns is updated so that all PRIMARY KEY columns are non-NULL, 241 ** only an INSERT is appears in the changeset. Similarly, if an existing row 242 ** with non-NULL PRIMARY KEY values is updated so that one or more of its 243 ** PRIMARY KEY columns are set to NULL, the resulting changeset contains a 244 ** DELETE change only. 245 ** 246 ** The contents of a changeset may be traversed using an iterator created 247 ** using the [sqlite3changeset_start()] API. A changeset may be applied to 248 ** a database with a compatible schema using the [sqlite3changeset_apply()] 249 ** API. 250 ** 251 ** Within a changeset generated by this function, all changes related to a 252 ** single table are grouped together. In other words, when iterating through 253 ** a changeset or when applying a changeset to a database, all changes related 254 ** to a single table are processed before moving on to the next table. Tables 255 ** are sorted in the same order in which they were attached (or auto-attached) 256 ** to the sqlite3_session object. The order in which the changes related to 257 ** a single table are stored is undefined. 258 ** 259 ** Following a successful call to this function, it is the responsibility of 260 ** the caller to eventually free the buffer that *ppChangeset points to using 261 ** [sqlite3_free()]. 262 ** 263 ** <h3>Changeset Generation</h3> 264 ** 265 ** Once a table has been attached to a session object, the session object 266 ** records the primary key values of all new rows inserted into the table. 267 ** It also records the original primary key and other column values of any 268 ** deleted or updated rows. For each unique primary key value, data is only 269 ** recorded once - the first time a row with said primary key is inserted, 270 ** updated or deleted in the lifetime of the session. 271 ** 272 ** There is one exception to the previous paragraph: when a row is inserted, 273 ** updated or deleted, if one or more of its primary key columns contain a 274 ** NULL value, no record of the change is made. 275 ** 276 ** The session object therefore accumulates two types of records - those 277 ** that consist of primary key values only (created when the user inserts 278 ** a new record) and those that consist of the primary key values and the 279 ** original values of other table columns (created when the users deletes 280 ** or updates a record). 281 ** 282 ** When this function is called, the requested changeset is created using 283 ** both the accumulated records and the current contents of the database 284 ** file. Specifically: 285 ** 286 ** <ul> 287 ** <li> For each record generated by an insert, the database is queried 288 ** for a row with a matching primary key. If one is found, an INSERT 289 ** change is added to the changeset. If no such row is found, no change 290 ** is added to the changeset. 291 ** 292 ** <li> For each record generated by an update or delete, the database is 293 ** queried for a row with a matching primary key. If such a row is 294 ** found and one or more of the non-primary key fields have been 295 ** modified from their original values, an UPDATE change is added to 296 ** the changeset. Or, if no such row is found in the table, a DELETE 297 ** change is added to the changeset. If there is a row with a matching 298 ** primary key in the database, but all fields contain their original 299 ** values, no change is added to the changeset. 300 ** </ul> 301 ** 302 ** This means, amongst other things, that if a row is inserted and then later 303 ** deleted while a session object is active, neither the insert nor the delete 304 ** will be present in the changeset. Or if a row is deleted and then later a 305 ** row with the same primary key values inserted while a session object is 306 ** active, the resulting changeset will contain an UPDATE change instead of 307 ** a DELETE and an INSERT. 308 ** 309 ** When a session object is disabled (see the [sqlite3session_enable()] API), 310 ** it does not accumulate records when rows are inserted, updated or deleted. 311 ** This may appear to have some counter-intuitive effects if a single row 312 ** is written to more than once during a session. For example, if a row 313 ** is inserted while a session object is enabled, then later deleted while 314 ** the same session object is disabled, no INSERT record will appear in the 315 ** changeset, even though the delete took place while the session was disabled. 316 ** Or, if one field of a row is updated while a session is disabled, and 317 ** another field of the same row is updated while the session is enabled, the 318 ** resulting changeset will contain an UPDATE change that updates both fields. 319 */ 320 int sqlite3session_changeset( 321 sqlite3_session *pSession, /* Session object */ 322 int *pnChangeset, /* OUT: Size of buffer at *ppChangeset */ 323 void **ppChangeset /* OUT: Buffer containing changeset */ 324 ); 325 326 /* 327 ** CAPI3REF: Load The Difference Between Tables Into A Session 328 ** METHOD: sqlite3_session 329 ** 330 ** If it is not already attached to the session object passed as the first 331 ** argument, this function attaches table zTbl in the same manner as the 332 ** [sqlite3session_attach()] function. If zTbl does not exist, or if it 333 ** does not have a primary key, this function is a no-op (but does not return 334 ** an error). 335 ** 336 ** Argument zFromDb must be the name of a database ("main", "temp" etc.) 337 ** attached to the same database handle as the session object that contains 338 ** a table compatible with the table attached to the session by this function. 339 ** A table is considered compatible if it: 340 ** 341 ** <ul> 342 ** <li> Has the same name, 343 ** <li> Has the same set of columns declared in the same order, and 344 ** <li> Has the same PRIMARY KEY definition. 345 ** </ul> 346 ** 347 ** If the tables are not compatible, SQLITE_SCHEMA is returned. If the tables 348 ** are compatible but do not have any PRIMARY KEY columns, it is not an error 349 ** but no changes are added to the session object. As with other session 350 ** APIs, tables without PRIMARY KEYs are simply ignored. 351 ** 352 ** This function adds a set of changes to the session object that could be 353 ** used to update the table in database zFrom (call this the "from-table") 354 ** so that its content is the same as the table attached to the session 355 ** object (call this the "to-table"). Specifically: 356 ** 357 ** <ul> 358 ** <li> For each row (primary key) that exists in the to-table but not in 359 ** the from-table, an INSERT record is added to the session object. 360 ** 361 ** <li> For each row (primary key) that exists in the to-table but not in 362 ** the from-table, a DELETE record is added to the session object. 363 ** 364 ** <li> For each row (primary key) that exists in both tables, but features 365 ** different non-PK values in each, an UPDATE record is added to the 366 ** session. 367 ** </ul> 368 ** 369 ** To clarify, if this function is called and then a changeset constructed 370 ** using [sqlite3session_changeset()], then after applying that changeset to 371 ** database zFrom the contents of the two compatible tables would be 372 ** identical. 373 ** 374 ** It an error if database zFrom does not exist or does not contain the 375 ** required compatible table. 376 ** 377 ** If the operation successful, SQLITE_OK is returned. Otherwise, an SQLite 378 ** error code. In this case, if argument pzErrMsg is not NULL, *pzErrMsg 379 ** may be set to point to a buffer containing an English language error 380 ** message. It is the responsibility of the caller to free this buffer using 381 ** sqlite3_free(). 382 */ 383 int sqlite3session_diff( 384 sqlite3_session *pSession, 385 const char *zFromDb, 386 const char *zTbl, 387 char **pzErrMsg 388 ); 389 390 391 /* 392 ** CAPI3REF: Generate A Patchset From A Session Object 393 ** METHOD: sqlite3_session 394 ** 395 ** The differences between a patchset and a changeset are that: 396 ** 397 ** <ul> 398 ** <li> DELETE records consist of the primary key fields only. The 399 ** original values of other fields are omitted. 400 ** <li> The original values of any modified fields are omitted from 401 ** UPDATE records. 402 ** </ul> 403 ** 404 ** A patchset blob may be used with up to date versions of all 405 ** sqlite3changeset_xxx API functions except for sqlite3changeset_invert(), 406 ** which returns SQLITE_CORRUPT if it is passed a patchset. Similarly, 407 ** attempting to use a patchset blob with old versions of the 408 ** sqlite3changeset_xxx APIs also provokes an SQLITE_CORRUPT error. 409 ** 410 ** Because the non-primary key "old.*" fields are omitted, no 411 ** SQLITE_CHANGESET_DATA conflicts can be detected or reported if a patchset 412 ** is passed to the sqlite3changeset_apply() API. Other conflict types work 413 ** in the same way as for changesets. 414 ** 415 ** Changes within a patchset are ordered in the same way as for changesets 416 ** generated by the sqlite3session_changeset() function (i.e. all changes for 417 ** a single table are grouped together, tables appear in the order in which 418 ** they were attached to the session object). 419 */ 420 int sqlite3session_patchset( 421 sqlite3_session *pSession, /* Session object */ 422 int *pnPatchset, /* OUT: Size of buffer at *ppPatchset */ 423 void **ppPatchset /* OUT: Buffer containing patchset */ 424 ); 425 426 /* 427 ** CAPI3REF: Test if a changeset has recorded any changes. 428 ** 429 ** Return non-zero if no changes to attached tables have been recorded by 430 ** the session object passed as the first argument. Otherwise, if one or 431 ** more changes have been recorded, return zero. 432 ** 433 ** Even if this function returns zero, it is possible that calling 434 ** [sqlite3session_changeset()] on the session handle may still return a 435 ** changeset that contains no changes. This can happen when a row in 436 ** an attached table is modified and then later on the original values 437 ** are restored. However, if this function returns non-zero, then it is 438 ** guaranteed that a call to sqlite3session_changeset() will return a 439 ** changeset containing zero changes. 440 */ 441 int sqlite3session_isempty(sqlite3_session *pSession); 442 443 /* 444 ** CAPI3REF: Create An Iterator To Traverse A Changeset 445 ** CONSTRUCTOR: sqlite3_changeset_iter 446 ** 447 ** Create an iterator used to iterate through the contents of a changeset. 448 ** If successful, *pp is set to point to the iterator handle and SQLITE_OK 449 ** is returned. Otherwise, if an error occurs, *pp is set to zero and an 450 ** SQLite error code is returned. 451 ** 452 ** The following functions can be used to advance and query a changeset 453 ** iterator created by this function: 454 ** 455 ** <ul> 456 ** <li> [sqlite3changeset_next()] 457 ** <li> [sqlite3changeset_op()] 458 ** <li> [sqlite3changeset_new()] 459 ** <li> [sqlite3changeset_old()] 460 ** </ul> 461 ** 462 ** It is the responsibility of the caller to eventually destroy the iterator 463 ** by passing it to [sqlite3changeset_finalize()]. The buffer containing the 464 ** changeset (pChangeset) must remain valid until after the iterator is 465 ** destroyed. 466 ** 467 ** Assuming the changeset blob was created by one of the 468 ** [sqlite3session_changeset()], [sqlite3changeset_concat()] or 469 ** [sqlite3changeset_invert()] functions, all changes within the changeset 470 ** that apply to a single table are grouped together. This means that when 471 ** an application iterates through a changeset using an iterator created by 472 ** this function, all changes that relate to a single table are visited 473 ** consecutively. There is no chance that the iterator will visit a change 474 ** the applies to table X, then one for table Y, and then later on visit 475 ** another change for table X. 476 ** 477 ** The behavior of sqlite3changeset_start_v2() and its streaming equivalent 478 ** may be modified by passing a combination of 479 ** [SQLITE_CHANGESETSTART_INVERT | supported flags] as the 4th parameter. 480 ** 481 ** Note that the sqlite3changeset_start_v2() API is still <b>experimental</b> 482 ** and therefore subject to change. 483 */ 484 int sqlite3changeset_start( 485 sqlite3_changeset_iter **pp, /* OUT: New changeset iterator handle */ 486 int nChangeset, /* Size of changeset blob in bytes */ 487 void *pChangeset /* Pointer to blob containing changeset */ 488 ); 489 int sqlite3changeset_start_v2( 490 sqlite3_changeset_iter **pp, /* OUT: New changeset iterator handle */ 491 int nChangeset, /* Size of changeset blob in bytes */ 492 void *pChangeset, /* Pointer to blob containing changeset */ 493 int flags /* SESSION_CHANGESETSTART_* flags */ 494 ); 495 496 /* 497 ** CAPI3REF: Flags for sqlite3changeset_start_v2 498 ** 499 ** The following flags may passed via the 4th parameter to 500 ** [sqlite3changeset_start_v2] and [sqlite3changeset_start_v2_strm]: 501 ** 502 ** <dt>SQLITE_CHANGESETAPPLY_INVERT <dd> 503 ** Invert the changeset while iterating through it. This is equivalent to 504 ** inverting a changeset using sqlite3changeset_invert() before applying it. 505 ** It is an error to specify this flag with a patchset. 506 */ 507 #define SQLITE_CHANGESETSTART_INVERT 0x0002 508 509 510 /* 511 ** CAPI3REF: Advance A Changeset Iterator 512 ** METHOD: sqlite3_changeset_iter 513 ** 514 ** This function may only be used with iterators created by function 515 ** [sqlite3changeset_start()]. If it is called on an iterator passed to 516 ** a conflict-handler callback by [sqlite3changeset_apply()], SQLITE_MISUSE 517 ** is returned and the call has no effect. 518 ** 519 ** Immediately after an iterator is created by sqlite3changeset_start(), it 520 ** does not point to any change in the changeset. Assuming the changeset 521 ** is not empty, the first call to this function advances the iterator to 522 ** point to the first change in the changeset. Each subsequent call advances 523 ** the iterator to point to the next change in the changeset (if any). If 524 ** no error occurs and the iterator points to a valid change after a call 525 ** to sqlite3changeset_next() has advanced it, SQLITE_ROW is returned. 526 ** Otherwise, if all changes in the changeset have already been visited, 527 ** SQLITE_DONE is returned. 528 ** 529 ** If an error occurs, an SQLite error code is returned. Possible error 530 ** codes include SQLITE_CORRUPT (if the changeset buffer is corrupt) or 531 ** SQLITE_NOMEM. 532 */ 533 int sqlite3changeset_next(sqlite3_changeset_iter *pIter); 534 535 /* 536 ** CAPI3REF: Obtain The Current Operation From A Changeset Iterator 537 ** METHOD: sqlite3_changeset_iter 538 ** 539 ** The pIter argument passed to this function may either be an iterator 540 ** passed to a conflict-handler by [sqlite3changeset_apply()], or an iterator 541 ** created by [sqlite3changeset_start()]. In the latter case, the most recent 542 ** call to [sqlite3changeset_next()] must have returned [SQLITE_ROW]. If this 543 ** is not the case, this function returns [SQLITE_MISUSE]. 544 ** 545 ** If argument pzTab is not NULL, then *pzTab is set to point to a 546 ** nul-terminated utf-8 encoded string containing the name of the table 547 ** affected by the current change. The buffer remains valid until either 548 ** sqlite3changeset_next() is called on the iterator or until the 549 ** conflict-handler function returns. If pnCol is not NULL, then *pnCol is 550 ** set to the number of columns in the table affected by the change. If 551 ** pbIncorrect is not NULL, then *pbIndirect is set to true (1) if the change 552 ** is an indirect change, or false (0) otherwise. See the documentation for 553 ** [sqlite3session_indirect()] for a description of direct and indirect 554 ** changes. Finally, if pOp is not NULL, then *pOp is set to one of 555 ** [SQLITE_INSERT], [SQLITE_DELETE] or [SQLITE_UPDATE], depending on the 556 ** type of change that the iterator currently points to. 557 ** 558 ** If no error occurs, SQLITE_OK is returned. If an error does occur, an 559 ** SQLite error code is returned. The values of the output variables may not 560 ** be trusted in this case. 561 */ 562 int sqlite3changeset_op( 563 sqlite3_changeset_iter *pIter, /* Iterator object */ 564 const char **pzTab, /* OUT: Pointer to table name */ 565 int *pnCol, /* OUT: Number of columns in table */ 566 int *pOp, /* OUT: SQLITE_INSERT, DELETE or UPDATE */ 567 int *pbIndirect /* OUT: True for an 'indirect' change */ 568 ); 569 570 /* 571 ** CAPI3REF: Obtain The Primary Key Definition Of A Table 572 ** METHOD: sqlite3_changeset_iter 573 ** 574 ** For each modified table, a changeset includes the following: 575 ** 576 ** <ul> 577 ** <li> The number of columns in the table, and 578 ** <li> Which of those columns make up the tables PRIMARY KEY. 579 ** </ul> 580 ** 581 ** This function is used to find which columns comprise the PRIMARY KEY of 582 ** the table modified by the change that iterator pIter currently points to. 583 ** If successful, *pabPK is set to point to an array of nCol entries, where 584 ** nCol is the number of columns in the table. Elements of *pabPK are set to 585 ** 0x01 if the corresponding column is part of the tables primary key, or 586 ** 0x00 if it is not. 587 ** 588 ** If argument pnCol is not NULL, then *pnCol is set to the number of columns 589 ** in the table. 590 ** 591 ** If this function is called when the iterator does not point to a valid 592 ** entry, SQLITE_MISUSE is returned and the output variables zeroed. Otherwise, 593 ** SQLITE_OK is returned and the output variables populated as described 594 ** above. 595 */ 596 int sqlite3changeset_pk( 597 sqlite3_changeset_iter *pIter, /* Iterator object */ 598 unsigned char **pabPK, /* OUT: Array of boolean - true for PK cols */ 599 int *pnCol /* OUT: Number of entries in output array */ 600 ); 601 602 /* 603 ** CAPI3REF: Obtain old.* Values From A Changeset Iterator 604 ** METHOD: sqlite3_changeset_iter 605 ** 606 ** The pIter argument passed to this function may either be an iterator 607 ** passed to a conflict-handler by [sqlite3changeset_apply()], or an iterator 608 ** created by [sqlite3changeset_start()]. In the latter case, the most recent 609 ** call to [sqlite3changeset_next()] must have returned SQLITE_ROW. 610 ** Furthermore, it may only be called if the type of change that the iterator 611 ** currently points to is either [SQLITE_DELETE] or [SQLITE_UPDATE]. Otherwise, 612 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL. 613 ** 614 ** Argument iVal must be greater than or equal to 0, and less than the number 615 ** of columns in the table affected by the current change. Otherwise, 616 ** [SQLITE_RANGE] is returned and *ppValue is set to NULL. 617 ** 618 ** If successful, this function sets *ppValue to point to a protected 619 ** sqlite3_value object containing the iVal'th value from the vector of 620 ** original row values stored as part of the UPDATE or DELETE change and 621 ** returns SQLITE_OK. The name of the function comes from the fact that this 622 ** is similar to the "old.*" columns available to update or delete triggers. 623 ** 624 ** If some other error occurs (e.g. an OOM condition), an SQLite error code 625 ** is returned and *ppValue is set to NULL. 626 */ 627 int sqlite3changeset_old( 628 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 629 int iVal, /* Column number */ 630 sqlite3_value **ppValue /* OUT: Old value (or NULL pointer) */ 631 ); 632 633 /* 634 ** CAPI3REF: Obtain new.* Values From A Changeset Iterator 635 ** METHOD: sqlite3_changeset_iter 636 ** 637 ** The pIter argument passed to this function may either be an iterator 638 ** passed to a conflict-handler by [sqlite3changeset_apply()], or an iterator 639 ** created by [sqlite3changeset_start()]. In the latter case, the most recent 640 ** call to [sqlite3changeset_next()] must have returned SQLITE_ROW. 641 ** Furthermore, it may only be called if the type of change that the iterator 642 ** currently points to is either [SQLITE_UPDATE] or [SQLITE_INSERT]. Otherwise, 643 ** this function returns [SQLITE_MISUSE] and sets *ppValue to NULL. 644 ** 645 ** Argument iVal must be greater than or equal to 0, and less than the number 646 ** of columns in the table affected by the current change. Otherwise, 647 ** [SQLITE_RANGE] is returned and *ppValue is set to NULL. 648 ** 649 ** If successful, this function sets *ppValue to point to a protected 650 ** sqlite3_value object containing the iVal'th value from the vector of 651 ** new row values stored as part of the UPDATE or INSERT change and 652 ** returns SQLITE_OK. If the change is an UPDATE and does not include 653 ** a new value for the requested column, *ppValue is set to NULL and 654 ** SQLITE_OK returned. The name of the function comes from the fact that 655 ** this is similar to the "new.*" columns available to update or delete 656 ** triggers. 657 ** 658 ** If some other error occurs (e.g. an OOM condition), an SQLite error code 659 ** is returned and *ppValue is set to NULL. 660 */ 661 int sqlite3changeset_new( 662 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 663 int iVal, /* Column number */ 664 sqlite3_value **ppValue /* OUT: New value (or NULL pointer) */ 665 ); 666 667 /* 668 ** CAPI3REF: Obtain Conflicting Row Values From A Changeset Iterator 669 ** METHOD: sqlite3_changeset_iter 670 ** 671 ** This function should only be used with iterator objects passed to a 672 ** conflict-handler callback by [sqlite3changeset_apply()] with either 673 ** [SQLITE_CHANGESET_DATA] or [SQLITE_CHANGESET_CONFLICT]. If this function 674 ** is called on any other iterator, [SQLITE_MISUSE] is returned and *ppValue 675 ** is set to NULL. 676 ** 677 ** Argument iVal must be greater than or equal to 0, and less than the number 678 ** of columns in the table affected by the current change. Otherwise, 679 ** [SQLITE_RANGE] is returned and *ppValue is set to NULL. 680 ** 681 ** If successful, this function sets *ppValue to point to a protected 682 ** sqlite3_value object containing the iVal'th value from the 683 ** "conflicting row" associated with the current conflict-handler callback 684 ** and returns SQLITE_OK. 685 ** 686 ** If some other error occurs (e.g. an OOM condition), an SQLite error code 687 ** is returned and *ppValue is set to NULL. 688 */ 689 int sqlite3changeset_conflict( 690 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 691 int iVal, /* Column number */ 692 sqlite3_value **ppValue /* OUT: Value from conflicting row */ 693 ); 694 695 /* 696 ** CAPI3REF: Determine The Number Of Foreign Key Constraint Violations 697 ** METHOD: sqlite3_changeset_iter 698 ** 699 ** This function may only be called with an iterator passed to an 700 ** SQLITE_CHANGESET_FOREIGN_KEY conflict handler callback. In this case 701 ** it sets the output variable to the total number of known foreign key 702 ** violations in the destination database and returns SQLITE_OK. 703 ** 704 ** In all other cases this function returns SQLITE_MISUSE. 705 */ 706 int sqlite3changeset_fk_conflicts( 707 sqlite3_changeset_iter *pIter, /* Changeset iterator */ 708 int *pnOut /* OUT: Number of FK violations */ 709 ); 710 711 712 /* 713 ** CAPI3REF: Finalize A Changeset Iterator 714 ** METHOD: sqlite3_changeset_iter 715 ** 716 ** This function is used to finalize an iterator allocated with 717 ** [sqlite3changeset_start()]. 718 ** 719 ** This function should only be called on iterators created using the 720 ** [sqlite3changeset_start()] function. If an application calls this 721 ** function with an iterator passed to a conflict-handler by 722 ** [sqlite3changeset_apply()], [SQLITE_MISUSE] is immediately returned and the 723 ** call has no effect. 724 ** 725 ** If an error was encountered within a call to an sqlite3changeset_xxx() 726 ** function (for example an [SQLITE_CORRUPT] in [sqlite3changeset_next()] or an 727 ** [SQLITE_NOMEM] in [sqlite3changeset_new()]) then an error code corresponding 728 ** to that error is returned by this function. Otherwise, SQLITE_OK is 729 ** returned. This is to allow the following pattern (pseudo-code): 730 ** 731 ** <pre> 732 ** sqlite3changeset_start(); 733 ** while( SQLITE_ROW==sqlite3changeset_next() ){ 734 ** // Do something with change. 735 ** } 736 ** rc = sqlite3changeset_finalize(); 737 ** if( rc!=SQLITE_OK ){ 738 ** // An error has occurred 739 ** } 740 ** </pre> 741 */ 742 int sqlite3changeset_finalize(sqlite3_changeset_iter *pIter); 743 744 /* 745 ** CAPI3REF: Invert A Changeset 746 ** 747 ** This function is used to "invert" a changeset object. Applying an inverted 748 ** changeset to a database reverses the effects of applying the uninverted 749 ** changeset. Specifically: 750 ** 751 ** <ul> 752 ** <li> Each DELETE change is changed to an INSERT, and 753 ** <li> Each INSERT change is changed to a DELETE, and 754 ** <li> For each UPDATE change, the old.* and new.* values are exchanged. 755 ** </ul> 756 ** 757 ** This function does not change the order in which changes appear within 758 ** the changeset. It merely reverses the sense of each individual change. 759 ** 760 ** If successful, a pointer to a buffer containing the inverted changeset 761 ** is stored in *ppOut, the size of the same buffer is stored in *pnOut, and 762 ** SQLITE_OK is returned. If an error occurs, both *pnOut and *ppOut are 763 ** zeroed and an SQLite error code returned. 764 ** 765 ** It is the responsibility of the caller to eventually call sqlite3_free() 766 ** on the *ppOut pointer to free the buffer allocation following a successful 767 ** call to this function. 768 ** 769 ** WARNING/TODO: This function currently assumes that the input is a valid 770 ** changeset. If it is not, the results are undefined. 771 */ 772 int sqlite3changeset_invert( 773 int nIn, const void *pIn, /* Input changeset */ 774 int *pnOut, void **ppOut /* OUT: Inverse of input */ 775 ); 776 777 /* 778 ** CAPI3REF: Concatenate Two Changeset Objects 779 ** 780 ** This function is used to concatenate two changesets, A and B, into a 781 ** single changeset. The result is a changeset equivalent to applying 782 ** changeset A followed by changeset B. 783 ** 784 ** This function combines the two input changesets using an 785 ** sqlite3_changegroup object. Calling it produces similar results as the 786 ** following code fragment: 787 ** 788 ** <pre> 789 ** sqlite3_changegroup *pGrp; 790 ** rc = sqlite3_changegroup_new(&pGrp); 791 ** if( rc==SQLITE_OK ) rc = sqlite3changegroup_add(pGrp, nA, pA); 792 ** if( rc==SQLITE_OK ) rc = sqlite3changegroup_add(pGrp, nB, pB); 793 ** if( rc==SQLITE_OK ){ 794 ** rc = sqlite3changegroup_output(pGrp, pnOut, ppOut); 795 ** }else{ 796 ** *ppOut = 0; 797 ** *pnOut = 0; 798 ** } 799 ** </pre> 800 ** 801 ** Refer to the sqlite3_changegroup documentation below for details. 802 */ 803 int sqlite3changeset_concat( 804 int nA, /* Number of bytes in buffer pA */ 805 void *pA, /* Pointer to buffer containing changeset A */ 806 int nB, /* Number of bytes in buffer pB */ 807 void *pB, /* Pointer to buffer containing changeset B */ 808 int *pnOut, /* OUT: Number of bytes in output changeset */ 809 void **ppOut /* OUT: Buffer containing output changeset */ 810 ); 811 812 813 /* 814 ** CAPI3REF: Changegroup Handle 815 ** 816 ** A changegroup is an object used to combine two or more 817 ** [changesets] or [patchsets] 818 */ 819 typedef struct sqlite3_changegroup sqlite3_changegroup; 820 821 /* 822 ** CAPI3REF: Create A New Changegroup Object 823 ** CONSTRUCTOR: sqlite3_changegroup 824 ** 825 ** An sqlite3_changegroup object is used to combine two or more changesets 826 ** (or patchsets) into a single changeset (or patchset). A single changegroup 827 ** object may combine changesets or patchsets, but not both. The output is 828 ** always in the same format as the input. 829 ** 830 ** If successful, this function returns SQLITE_OK and populates (*pp) with 831 ** a pointer to a new sqlite3_changegroup object before returning. The caller 832 ** should eventually free the returned object using a call to 833 ** sqlite3changegroup_delete(). If an error occurs, an SQLite error code 834 ** (i.e. SQLITE_NOMEM) is returned and *pp is set to NULL. 835 ** 836 ** The usual usage pattern for an sqlite3_changegroup object is as follows: 837 ** 838 ** <ul> 839 ** <li> It is created using a call to sqlite3changegroup_new(). 840 ** 841 ** <li> Zero or more changesets (or patchsets) are added to the object 842 ** by calling sqlite3changegroup_add(). 843 ** 844 ** <li> The result of combining all input changesets together is obtained 845 ** by the application via a call to sqlite3changegroup_output(). 846 ** 847 ** <li> The object is deleted using a call to sqlite3changegroup_delete(). 848 ** </ul> 849 ** 850 ** Any number of calls to add() and output() may be made between the calls to 851 ** new() and delete(), and in any order. 852 ** 853 ** As well as the regular sqlite3changegroup_add() and 854 ** sqlite3changegroup_output() functions, also available are the streaming 855 ** versions sqlite3changegroup_add_strm() and sqlite3changegroup_output_strm(). 856 */ 857 int sqlite3changegroup_new(sqlite3_changegroup **pp); 858 859 /* 860 ** CAPI3REF: Add A Changeset To A Changegroup 861 ** METHOD: sqlite3_changegroup 862 ** 863 ** Add all changes within the changeset (or patchset) in buffer pData (size 864 ** nData bytes) to the changegroup. 865 ** 866 ** If the buffer contains a patchset, then all prior calls to this function 867 ** on the same changegroup object must also have specified patchsets. Or, if 868 ** the buffer contains a changeset, so must have the earlier calls to this 869 ** function. Otherwise, SQLITE_ERROR is returned and no changes are added 870 ** to the changegroup. 871 ** 872 ** Rows within the changeset and changegroup are identified by the values in 873 ** their PRIMARY KEY columns. A change in the changeset is considered to 874 ** apply to the same row as a change already present in the changegroup if 875 ** the two rows have the same primary key. 876 ** 877 ** Changes to rows that do not already appear in the changegroup are 878 ** simply copied into it. Or, if both the new changeset and the changegroup 879 ** contain changes that apply to a single row, the final contents of the 880 ** changegroup depends on the type of each change, as follows: 881 ** 882 ** <table border=1 style="margin-left:8ex;margin-right:8ex"> 883 ** <tr><th style="white-space:pre">Existing Change </th> 884 ** <th style="white-space:pre">New Change </th> 885 ** <th>Output Change 886 ** <tr><td>INSERT <td>INSERT <td> 887 ** The new change is ignored. This case does not occur if the new 888 ** changeset was recorded immediately after the changesets already 889 ** added to the changegroup. 890 ** <tr><td>INSERT <td>UPDATE <td> 891 ** The INSERT change remains in the changegroup. The values in the 892 ** INSERT change are modified as if the row was inserted by the 893 ** existing change and then updated according to the new change. 894 ** <tr><td>INSERT <td>DELETE <td> 895 ** The existing INSERT is removed from the changegroup. The DELETE is 896 ** not added. 897 ** <tr><td>UPDATE <td>INSERT <td> 898 ** The new change is ignored. This case does not occur if the new 899 ** changeset was recorded immediately after the changesets already 900 ** added to the changegroup. 901 ** <tr><td>UPDATE <td>UPDATE <td> 902 ** The existing UPDATE remains within the changegroup. It is amended 903 ** so that the accompanying values are as if the row was updated once 904 ** by the existing change and then again by the new change. 905 ** <tr><td>UPDATE <td>DELETE <td> 906 ** The existing UPDATE is replaced by the new DELETE within the 907 ** changegroup. 908 ** <tr><td>DELETE <td>INSERT <td> 909 ** If one or more of the column values in the row inserted by the 910 ** new change differ from those in the row deleted by the existing 911 ** change, the existing DELETE is replaced by an UPDATE within the 912 ** changegroup. Otherwise, if the inserted row is exactly the same 913 ** as the deleted row, the existing DELETE is simply discarded. 914 ** <tr><td>DELETE <td>UPDATE <td> 915 ** The new change is ignored. This case does not occur if the new 916 ** changeset was recorded immediately after the changesets already 917 ** added to the changegroup. 918 ** <tr><td>DELETE <td>DELETE <td> 919 ** The new change is ignored. This case does not occur if the new 920 ** changeset was recorded immediately after the changesets already 921 ** added to the changegroup. 922 ** </table> 923 ** 924 ** If the new changeset contains changes to a table that is already present 925 ** in the changegroup, then the number of columns and the position of the 926 ** primary key columns for the table must be consistent. If this is not the 927 ** case, this function fails with SQLITE_SCHEMA. If the input changeset 928 ** appears to be corrupt and the corruption is detected, SQLITE_CORRUPT is 929 ** returned. Or, if an out-of-memory condition occurs during processing, this 930 ** function returns SQLITE_NOMEM. In all cases, if an error occurs the 931 ** final contents of the changegroup is undefined. 932 ** 933 ** If no error occurs, SQLITE_OK is returned. 934 */ 935 int sqlite3changegroup_add(sqlite3_changegroup*, int nData, void *pData); 936 937 /* 938 ** CAPI3REF: Obtain A Composite Changeset From A Changegroup 939 ** METHOD: sqlite3_changegroup 940 ** 941 ** Obtain a buffer containing a changeset (or patchset) representing the 942 ** current contents of the changegroup. If the inputs to the changegroup 943 ** were themselves changesets, the output is a changeset. Or, if the 944 ** inputs were patchsets, the output is also a patchset. 945 ** 946 ** As with the output of the sqlite3session_changeset() and 947 ** sqlite3session_patchset() functions, all changes related to a single 948 ** table are grouped together in the output of this function. Tables appear 949 ** in the same order as for the very first changeset added to the changegroup. 950 ** If the second or subsequent changesets added to the changegroup contain 951 ** changes for tables that do not appear in the first changeset, they are 952 ** appended onto the end of the output changeset, again in the order in 953 ** which they are first encountered. 954 ** 955 ** If an error occurs, an SQLite error code is returned and the output 956 ** variables (*pnData) and (*ppData) are set to 0. Otherwise, SQLITE_OK 957 ** is returned and the output variables are set to the size of and a 958 ** pointer to the output buffer, respectively. In this case it is the 959 ** responsibility of the caller to eventually free the buffer using a 960 ** call to sqlite3_free(). 961 */ 962 int sqlite3changegroup_output( 963 sqlite3_changegroup*, 964 int *pnData, /* OUT: Size of output buffer in bytes */ 965 void **ppData /* OUT: Pointer to output buffer */ 966 ); 967 968 /* 969 ** CAPI3REF: Delete A Changegroup Object 970 ** DESTRUCTOR: sqlite3_changegroup 971 */ 972 void sqlite3changegroup_delete(sqlite3_changegroup*); 973 974 /* 975 ** CAPI3REF: Apply A Changeset To A Database 976 ** 977 ** Apply a changeset or patchset to a database. These functions attempt to 978 ** update the "main" database attached to handle db with the changes found in 979 ** the changeset passed via the second and third arguments. 980 ** 981 ** The fourth argument (xFilter) passed to these functions is the "filter 982 ** callback". If it is not NULL, then for each table affected by at least one 983 ** change in the changeset, the filter callback is invoked with 984 ** the table name as the second argument, and a copy of the context pointer 985 ** passed as the sixth argument as the first. If the "filter callback" 986 ** returns zero, then no attempt is made to apply any changes to the table. 987 ** Otherwise, if the return value is non-zero or the xFilter argument to 988 ** is NULL, all changes related to the table are attempted. 989 ** 990 ** For each table that is not excluded by the filter callback, this function 991 ** tests that the target database contains a compatible table. A table is 992 ** considered compatible if all of the following are true: 993 ** 994 ** <ul> 995 ** <li> The table has the same name as the name recorded in the 996 ** changeset, and 997 ** <li> The table has at least as many columns as recorded in the 998 ** changeset, and 999 ** <li> The table has primary key columns in the same position as 1000 ** recorded in the changeset. 1001 ** </ul> 1002 ** 1003 ** If there is no compatible table, it is not an error, but none of the 1004 ** changes associated with the table are applied. A warning message is issued 1005 ** via the sqlite3_log() mechanism with the error code SQLITE_SCHEMA. At most 1006 ** one such warning is issued for each table in the changeset. 1007 ** 1008 ** For each change for which there is a compatible table, an attempt is made 1009 ** to modify the table contents according to the UPDATE, INSERT or DELETE 1010 ** change. If a change cannot be applied cleanly, the conflict handler 1011 ** function passed as the fifth argument to sqlite3changeset_apply() may be 1012 ** invoked. A description of exactly when the conflict handler is invoked for 1013 ** each type of change is below. 1014 ** 1015 ** Unlike the xFilter argument, xConflict may not be passed NULL. The results 1016 ** of passing anything other than a valid function pointer as the xConflict 1017 ** argument are undefined. 1018 ** 1019 ** Each time the conflict handler function is invoked, it must return one 1020 ** of [SQLITE_CHANGESET_OMIT], [SQLITE_CHANGESET_ABORT] or 1021 ** [SQLITE_CHANGESET_REPLACE]. SQLITE_CHANGESET_REPLACE may only be returned 1022 ** if the second argument passed to the conflict handler is either 1023 ** SQLITE_CHANGESET_DATA or SQLITE_CHANGESET_CONFLICT. If the conflict-handler 1024 ** returns an illegal value, any changes already made are rolled back and 1025 ** the call to sqlite3changeset_apply() returns SQLITE_MISUSE. Different 1026 ** actions are taken by sqlite3changeset_apply() depending on the value 1027 ** returned by each invocation of the conflict-handler function. Refer to 1028 ** the documentation for the three 1029 ** [SQLITE_CHANGESET_OMIT|available return values] for details. 1030 ** 1031 ** <dl> 1032 ** <dt>DELETE Changes<dd> 1033 ** For each DELETE change, the function checks if the target database 1034 ** contains a row with the same primary key value (or values) as the 1035 ** original row values stored in the changeset. If it does, and the values 1036 ** stored in all non-primary key columns also match the values stored in 1037 ** the changeset the row is deleted from the target database. 1038 ** 1039 ** If a row with matching primary key values is found, but one or more of 1040 ** the non-primary key fields contains a value different from the original 1041 ** row value stored in the changeset, the conflict-handler function is 1042 ** invoked with [SQLITE_CHANGESET_DATA] as the second argument. If the 1043 ** database table has more columns than are recorded in the changeset, 1044 ** only the values of those non-primary key fields are compared against 1045 ** the current database contents - any trailing database table columns 1046 ** are ignored. 1047 ** 1048 ** If no row with matching primary key values is found in the database, 1049 ** the conflict-handler function is invoked with [SQLITE_CHANGESET_NOTFOUND] 1050 ** passed as the second argument. 1051 ** 1052 ** If the DELETE operation is attempted, but SQLite returns SQLITE_CONSTRAINT 1053 ** (which can only happen if a foreign key constraint is violated), the 1054 ** conflict-handler function is invoked with [SQLITE_CHANGESET_CONSTRAINT] 1055 ** passed as the second argument. This includes the case where the DELETE 1056 ** operation is attempted because an earlier call to the conflict handler 1057 ** function returned [SQLITE_CHANGESET_REPLACE]. 1058 ** 1059 ** <dt>INSERT Changes<dd> 1060 ** For each INSERT change, an attempt is made to insert the new row into 1061 ** the database. If the changeset row contains fewer fields than the 1062 ** database table, the trailing fields are populated with their default 1063 ** values. 1064 ** 1065 ** If the attempt to insert the row fails because the database already 1066 ** contains a row with the same primary key values, the conflict handler 1067 ** function is invoked with the second argument set to 1068 ** [SQLITE_CHANGESET_CONFLICT]. 1069 ** 1070 ** If the attempt to insert the row fails because of some other constraint 1071 ** violation (e.g. NOT NULL or UNIQUE), the conflict handler function is 1072 ** invoked with the second argument set to [SQLITE_CHANGESET_CONSTRAINT]. 1073 ** This includes the case where the INSERT operation is re-attempted because 1074 ** an earlier call to the conflict handler function returned 1075 ** [SQLITE_CHANGESET_REPLACE]. 1076 ** 1077 ** <dt>UPDATE Changes<dd> 1078 ** For each UPDATE change, the function checks if the target database 1079 ** contains a row with the same primary key value (or values) as the 1080 ** original row values stored in the changeset. If it does, and the values 1081 ** stored in all modified non-primary key columns also match the values 1082 ** stored in the changeset the row is updated within the target database. 1083 ** 1084 ** If a row with matching primary key values is found, but one or more of 1085 ** the modified non-primary key fields contains a value different from an 1086 ** original row value stored in the changeset, the conflict-handler function 1087 ** is invoked with [SQLITE_CHANGESET_DATA] as the second argument. Since 1088 ** UPDATE changes only contain values for non-primary key fields that are 1089 ** to be modified, only those fields need to match the original values to 1090 ** avoid the SQLITE_CHANGESET_DATA conflict-handler callback. 1091 ** 1092 ** If no row with matching primary key values is found in the database, 1093 ** the conflict-handler function is invoked with [SQLITE_CHANGESET_NOTFOUND] 1094 ** passed as the second argument. 1095 ** 1096 ** If the UPDATE operation is attempted, but SQLite returns 1097 ** SQLITE_CONSTRAINT, the conflict-handler function is invoked with 1098 ** [SQLITE_CHANGESET_CONSTRAINT] passed as the second argument. 1099 ** This includes the case where the UPDATE operation is attempted after 1100 ** an earlier call to the conflict handler function returned 1101 ** [SQLITE_CHANGESET_REPLACE]. 1102 ** </dl> 1103 ** 1104 ** It is safe to execute SQL statements, including those that write to the 1105 ** table that the callback related to, from within the xConflict callback. 1106 ** This can be used to further customize the applications conflict 1107 ** resolution strategy. 1108 ** 1109 ** All changes made by these functions are enclosed in a savepoint transaction. 1110 ** If any other error (aside from a constraint failure when attempting to 1111 ** write to the target database) occurs, then the savepoint transaction is 1112 ** rolled back, restoring the target database to its original state, and an 1113 ** SQLite error code returned. 1114 ** 1115 ** If the output parameters (ppRebase) and (pnRebase) are non-NULL and 1116 ** the input is a changeset (not a patchset), then sqlite3changeset_apply_v2() 1117 ** may set (*ppRebase) to point to a "rebase" that may be used with the 1118 ** sqlite3_rebaser APIs buffer before returning. In this case (*pnRebase) 1119 ** is set to the size of the buffer in bytes. It is the responsibility of the 1120 ** caller to eventually free any such buffer using sqlite3_free(). The buffer 1121 ** is only allocated and populated if one or more conflicts were encountered 1122 ** while applying the patchset. See comments surrounding the sqlite3_rebaser 1123 ** APIs for further details. 1124 ** 1125 ** The behavior of sqlite3changeset_apply_v2() and its streaming equivalent 1126 ** may be modified by passing a combination of 1127 ** [SQLITE_CHANGESETAPPLY_NOSAVEPOINT | supported flags] as the 9th parameter. 1128 ** 1129 ** Note that the sqlite3changeset_apply_v2() API is still <b>experimental</b> 1130 ** and therefore subject to change. 1131 */ 1132 int sqlite3changeset_apply( 1133 sqlite3 *db, /* Apply change to "main" db of this handle */ 1134 int nChangeset, /* Size of changeset in bytes */ 1135 void *pChangeset, /* Changeset blob */ 1136 int(*xFilter)( 1137 void *pCtx, /* Copy of sixth arg to _apply() */ 1138 const char *zTab /* Table name */ 1139 ), 1140 int(*xConflict)( 1141 void *pCtx, /* Copy of sixth arg to _apply() */ 1142 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 1143 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 1144 ), 1145 void *pCtx /* First argument passed to xConflict */ 1146 ); 1147 int sqlite3changeset_apply_v2( 1148 sqlite3 *db, /* Apply change to "main" db of this handle */ 1149 int nChangeset, /* Size of changeset in bytes */ 1150 void *pChangeset, /* Changeset blob */ 1151 int(*xFilter)( 1152 void *pCtx, /* Copy of sixth arg to _apply() */ 1153 const char *zTab /* Table name */ 1154 ), 1155 int(*xConflict)( 1156 void *pCtx, /* Copy of sixth arg to _apply() */ 1157 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 1158 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 1159 ), 1160 void *pCtx, /* First argument passed to xConflict */ 1161 void **ppRebase, int *pnRebase, /* OUT: Rebase data */ 1162 int flags /* SESSION_CHANGESETAPPLY_* flags */ 1163 ); 1164 1165 /* 1166 ** CAPI3REF: Flags for sqlite3changeset_apply_v2 1167 ** 1168 ** The following flags may passed via the 9th parameter to 1169 ** [sqlite3changeset_apply_v2] and [sqlite3changeset_apply_v2_strm]: 1170 ** 1171 ** <dl> 1172 ** <dt>SQLITE_CHANGESETAPPLY_NOSAVEPOINT <dd> 1173 ** Usually, the sessions module encloses all operations performed by 1174 ** a single call to apply_v2() or apply_v2_strm() in a [SAVEPOINT]. The 1175 ** SAVEPOINT is committed if the changeset or patchset is successfully 1176 ** applied, or rolled back if an error occurs. Specifying this flag 1177 ** causes the sessions module to omit this savepoint. In this case, if the 1178 ** caller has an open transaction or savepoint when apply_v2() is called, 1179 ** it may revert the partially applied changeset by rolling it back. 1180 ** 1181 ** <dt>SQLITE_CHANGESETAPPLY_INVERT <dd> 1182 ** Invert the changeset before applying it. This is equivalent to inverting 1183 ** a changeset using sqlite3changeset_invert() before applying it. It is 1184 ** an error to specify this flag with a patchset. 1185 */ 1186 #define SQLITE_CHANGESETAPPLY_NOSAVEPOINT 0x0001 1187 #define SQLITE_CHANGESETAPPLY_INVERT 0x0002 1188 1189 /* 1190 ** CAPI3REF: Constants Passed To The Conflict Handler 1191 ** 1192 ** Values that may be passed as the second argument to a conflict-handler. 1193 ** 1194 ** <dl> 1195 ** <dt>SQLITE_CHANGESET_DATA<dd> 1196 ** The conflict handler is invoked with CHANGESET_DATA as the second argument 1197 ** when processing a DELETE or UPDATE change if a row with the required 1198 ** PRIMARY KEY fields is present in the database, but one or more other 1199 ** (non primary-key) fields modified by the update do not contain the 1200 ** expected "before" values. 1201 ** 1202 ** The conflicting row, in this case, is the database row with the matching 1203 ** primary key. 1204 ** 1205 ** <dt>SQLITE_CHANGESET_NOTFOUND<dd> 1206 ** The conflict handler is invoked with CHANGESET_NOTFOUND as the second 1207 ** argument when processing a DELETE or UPDATE change if a row with the 1208 ** required PRIMARY KEY fields is not present in the database. 1209 ** 1210 ** There is no conflicting row in this case. The results of invoking the 1211 ** sqlite3changeset_conflict() API are undefined. 1212 ** 1213 ** <dt>SQLITE_CHANGESET_CONFLICT<dd> 1214 ** CHANGESET_CONFLICT is passed as the second argument to the conflict 1215 ** handler while processing an INSERT change if the operation would result 1216 ** in duplicate primary key values. 1217 ** 1218 ** The conflicting row in this case is the database row with the matching 1219 ** primary key. 1220 ** 1221 ** <dt>SQLITE_CHANGESET_FOREIGN_KEY<dd> 1222 ** If foreign key handling is enabled, and applying a changeset leaves the 1223 ** database in a state containing foreign key violations, the conflict 1224 ** handler is invoked with CHANGESET_FOREIGN_KEY as the second argument 1225 ** exactly once before the changeset is committed. If the conflict handler 1226 ** returns CHANGESET_OMIT, the changes, including those that caused the 1227 ** foreign key constraint violation, are committed. Or, if it returns 1228 ** CHANGESET_ABORT, the changeset is rolled back. 1229 ** 1230 ** No current or conflicting row information is provided. The only function 1231 ** it is possible to call on the supplied sqlite3_changeset_iter handle 1232 ** is sqlite3changeset_fk_conflicts(). 1233 ** 1234 ** <dt>SQLITE_CHANGESET_CONSTRAINT<dd> 1235 ** If any other constraint violation occurs while applying a change (i.e. 1236 ** a UNIQUE, CHECK or NOT NULL constraint), the conflict handler is 1237 ** invoked with CHANGESET_CONSTRAINT as the second argument. 1238 ** 1239 ** There is no conflicting row in this case. The results of invoking the 1240 ** sqlite3changeset_conflict() API are undefined. 1241 ** 1242 ** </dl> 1243 */ 1244 #define SQLITE_CHANGESET_DATA 1 1245 #define SQLITE_CHANGESET_NOTFOUND 2 1246 #define SQLITE_CHANGESET_CONFLICT 3 1247 #define SQLITE_CHANGESET_CONSTRAINT 4 1248 #define SQLITE_CHANGESET_FOREIGN_KEY 5 1249 1250 /* 1251 ** CAPI3REF: Constants Returned By The Conflict Handler 1252 ** 1253 ** A conflict handler callback must return one of the following three values. 1254 ** 1255 ** <dl> 1256 ** <dt>SQLITE_CHANGESET_OMIT<dd> 1257 ** If a conflict handler returns this value no special action is taken. The 1258 ** change that caused the conflict is not applied. The session module 1259 ** continues to the next change in the changeset. 1260 ** 1261 ** <dt>SQLITE_CHANGESET_REPLACE<dd> 1262 ** This value may only be returned if the second argument to the conflict 1263 ** handler was SQLITE_CHANGESET_DATA or SQLITE_CHANGESET_CONFLICT. If this 1264 ** is not the case, any changes applied so far are rolled back and the 1265 ** call to sqlite3changeset_apply() returns SQLITE_MISUSE. 1266 ** 1267 ** If CHANGESET_REPLACE is returned by an SQLITE_CHANGESET_DATA conflict 1268 ** handler, then the conflicting row is either updated or deleted, depending 1269 ** on the type of change. 1270 ** 1271 ** If CHANGESET_REPLACE is returned by an SQLITE_CHANGESET_CONFLICT conflict 1272 ** handler, then the conflicting row is removed from the database and a 1273 ** second attempt to apply the change is made. If this second attempt fails, 1274 ** the original row is restored to the database before continuing. 1275 ** 1276 ** <dt>SQLITE_CHANGESET_ABORT<dd> 1277 ** If this value is returned, any changes applied so far are rolled back 1278 ** and the call to sqlite3changeset_apply() returns SQLITE_ABORT. 1279 ** </dl> 1280 */ 1281 #define SQLITE_CHANGESET_OMIT 0 1282 #define SQLITE_CHANGESET_REPLACE 1 1283 #define SQLITE_CHANGESET_ABORT 2 1284 1285 /* 1286 ** CAPI3REF: Rebasing changesets 1287 ** EXPERIMENTAL 1288 ** 1289 ** Suppose there is a site hosting a database in state S0. And that 1290 ** modifications are made that move that database to state S1 and a 1291 ** changeset recorded (the "local" changeset). Then, a changeset based 1292 ** on S0 is received from another site (the "remote" changeset) and 1293 ** applied to the database. The database is then in state 1294 ** (S1+"remote"), where the exact state depends on any conflict 1295 ** resolution decisions (OMIT or REPLACE) made while applying "remote". 1296 ** Rebasing a changeset is to update it to take those conflict 1297 ** resolution decisions into account, so that the same conflicts 1298 ** do not have to be resolved elsewhere in the network. 1299 ** 1300 ** For example, if both the local and remote changesets contain an 1301 ** INSERT of the same key on "CREATE TABLE t1(a PRIMARY KEY, b)": 1302 ** 1303 ** local: INSERT INTO t1 VALUES(1, 'v1'); 1304 ** remote: INSERT INTO t1 VALUES(1, 'v2'); 1305 ** 1306 ** and the conflict resolution is REPLACE, then the INSERT change is 1307 ** removed from the local changeset (it was overridden). Or, if the 1308 ** conflict resolution was "OMIT", then the local changeset is modified 1309 ** to instead contain: 1310 ** 1311 ** UPDATE t1 SET b = 'v2' WHERE a=1; 1312 ** 1313 ** Changes within the local changeset are rebased as follows: 1314 ** 1315 ** <dl> 1316 ** <dt>Local INSERT<dd> 1317 ** This may only conflict with a remote INSERT. If the conflict 1318 ** resolution was OMIT, then add an UPDATE change to the rebased 1319 ** changeset. Or, if the conflict resolution was REPLACE, add 1320 ** nothing to the rebased changeset. 1321 ** 1322 ** <dt>Local DELETE<dd> 1323 ** This may conflict with a remote UPDATE or DELETE. In both cases the 1324 ** only possible resolution is OMIT. If the remote operation was a 1325 ** DELETE, then add no change to the rebased changeset. If the remote 1326 ** operation was an UPDATE, then the old.* fields of change are updated 1327 ** to reflect the new.* values in the UPDATE. 1328 ** 1329 ** <dt>Local UPDATE<dd> 1330 ** This may conflict with a remote UPDATE or DELETE. If it conflicts 1331 ** with a DELETE, and the conflict resolution was OMIT, then the update 1332 ** is changed into an INSERT. Any undefined values in the new.* record 1333 ** from the update change are filled in using the old.* values from 1334 ** the conflicting DELETE. Or, if the conflict resolution was REPLACE, 1335 ** the UPDATE change is simply omitted from the rebased changeset. 1336 ** 1337 ** If conflict is with a remote UPDATE and the resolution is OMIT, then 1338 ** the old.* values are rebased using the new.* values in the remote 1339 ** change. Or, if the resolution is REPLACE, then the change is copied 1340 ** into the rebased changeset with updates to columns also updated by 1341 ** the conflicting remote UPDATE removed. If this means no columns would 1342 ** be updated, the change is omitted. 1343 ** </dl> 1344 ** 1345 ** A local change may be rebased against multiple remote changes 1346 ** simultaneously. If a single key is modified by multiple remote 1347 ** changesets, they are combined as follows before the local changeset 1348 ** is rebased: 1349 ** 1350 ** <ul> 1351 ** <li> If there has been one or more REPLACE resolutions on a 1352 ** key, it is rebased according to a REPLACE. 1353 ** 1354 ** <li> If there have been no REPLACE resolutions on a key, then 1355 ** the local changeset is rebased according to the most recent 1356 ** of the OMIT resolutions. 1357 ** </ul> 1358 ** 1359 ** Note that conflict resolutions from multiple remote changesets are 1360 ** combined on a per-field basis, not per-row. This means that in the 1361 ** case of multiple remote UPDATE operations, some fields of a single 1362 ** local change may be rebased for REPLACE while others are rebased for 1363 ** OMIT. 1364 ** 1365 ** In order to rebase a local changeset, the remote changeset must first 1366 ** be applied to the local database using sqlite3changeset_apply_v2() and 1367 ** the buffer of rebase information captured. Then: 1368 ** 1369 ** <ol> 1370 ** <li> An sqlite3_rebaser object is created by calling 1371 ** sqlite3rebaser_create(). 1372 ** <li> The new object is configured with the rebase buffer obtained from 1373 ** sqlite3changeset_apply_v2() by calling sqlite3rebaser_configure(). 1374 ** If the local changeset is to be rebased against multiple remote 1375 ** changesets, then sqlite3rebaser_configure() should be called 1376 ** multiple times, in the same order that the multiple 1377 ** sqlite3changeset_apply_v2() calls were made. 1378 ** <li> Each local changeset is rebased by calling sqlite3rebaser_rebase(). 1379 ** <li> The sqlite3_rebaser object is deleted by calling 1380 ** sqlite3rebaser_delete(). 1381 ** </ol> 1382 */ 1383 typedef struct sqlite3_rebaser sqlite3_rebaser; 1384 1385 /* 1386 ** CAPI3REF: Create a changeset rebaser object. 1387 ** EXPERIMENTAL 1388 ** 1389 ** Allocate a new changeset rebaser object. If successful, set (*ppNew) to 1390 ** point to the new object and return SQLITE_OK. Otherwise, if an error 1391 ** occurs, return an SQLite error code (e.g. SQLITE_NOMEM) and set (*ppNew) 1392 ** to NULL. 1393 */ 1394 int sqlite3rebaser_create(sqlite3_rebaser **ppNew); 1395 1396 /* 1397 ** CAPI3REF: Configure a changeset rebaser object. 1398 ** EXPERIMENTAL 1399 ** 1400 ** Configure the changeset rebaser object to rebase changesets according 1401 ** to the conflict resolutions described by buffer pRebase (size nRebase 1402 ** bytes), which must have been obtained from a previous call to 1403 ** sqlite3changeset_apply_v2(). 1404 */ 1405 int sqlite3rebaser_configure( 1406 sqlite3_rebaser*, 1407 int nRebase, const void *pRebase 1408 ); 1409 1410 /* 1411 ** CAPI3REF: Rebase a changeset 1412 ** EXPERIMENTAL 1413 ** 1414 ** Argument pIn must point to a buffer containing a changeset nIn bytes 1415 ** in size. This function allocates and populates a buffer with a copy 1416 ** of the changeset rebased rebased according to the configuration of the 1417 ** rebaser object passed as the first argument. If successful, (*ppOut) 1418 ** is set to point to the new buffer containing the rebased changset and 1419 ** (*pnOut) to its size in bytes and SQLITE_OK returned. It is the 1420 ** responsibility of the caller to eventually free the new buffer using 1421 ** sqlite3_free(). Otherwise, if an error occurs, (*ppOut) and (*pnOut) 1422 ** are set to zero and an SQLite error code returned. 1423 */ 1424 int sqlite3rebaser_rebase( 1425 sqlite3_rebaser*, 1426 int nIn, const void *pIn, 1427 int *pnOut, void **ppOut 1428 ); 1429 1430 /* 1431 ** CAPI3REF: Delete a changeset rebaser object. 1432 ** EXPERIMENTAL 1433 ** 1434 ** Delete the changeset rebaser object and all associated resources. There 1435 ** should be one call to this function for each successful invocation 1436 ** of sqlite3rebaser_create(). 1437 */ 1438 void sqlite3rebaser_delete(sqlite3_rebaser *p); 1439 1440 /* 1441 ** CAPI3REF: Streaming Versions of API functions. 1442 ** 1443 ** The six streaming API xxx_strm() functions serve similar purposes to the 1444 ** corresponding non-streaming API functions: 1445 ** 1446 ** <table border=1 style="margin-left:8ex;margin-right:8ex"> 1447 ** <tr><th>Streaming function<th>Non-streaming equivalent</th> 1448 ** <tr><td>sqlite3changeset_apply_strm<td>[sqlite3changeset_apply] 1449 ** <tr><td>sqlite3changeset_apply_strm_v2<td>[sqlite3changeset_apply_v2] 1450 ** <tr><td>sqlite3changeset_concat_strm<td>[sqlite3changeset_concat] 1451 ** <tr><td>sqlite3changeset_invert_strm<td>[sqlite3changeset_invert] 1452 ** <tr><td>sqlite3changeset_start_strm<td>[sqlite3changeset_start] 1453 ** <tr><td>sqlite3session_changeset_strm<td>[sqlite3session_changeset] 1454 ** <tr><td>sqlite3session_patchset_strm<td>[sqlite3session_patchset] 1455 ** </table> 1456 ** 1457 ** Non-streaming functions that accept changesets (or patchsets) as input 1458 ** require that the entire changeset be stored in a single buffer in memory. 1459 ** Similarly, those that return a changeset or patchset do so by returning 1460 ** a pointer to a single large buffer allocated using sqlite3_malloc(). 1461 ** Normally this is convenient. However, if an application running in a 1462 ** low-memory environment is required to handle very large changesets, the 1463 ** large contiguous memory allocations required can become onerous. 1464 ** 1465 ** In order to avoid this problem, instead of a single large buffer, input 1466 ** is passed to a streaming API functions by way of a callback function that 1467 ** the sessions module invokes to incrementally request input data as it is 1468 ** required. In all cases, a pair of API function parameters such as 1469 ** 1470 ** <pre> 1471 ** int nChangeset, 1472 ** void *pChangeset, 1473 ** </pre> 1474 ** 1475 ** Is replaced by: 1476 ** 1477 ** <pre> 1478 ** int (*xInput)(void *pIn, void *pData, int *pnData), 1479 ** void *pIn, 1480 ** </pre> 1481 ** 1482 ** Each time the xInput callback is invoked by the sessions module, the first 1483 ** argument passed is a copy of the supplied pIn context pointer. The second 1484 ** argument, pData, points to a buffer (*pnData) bytes in size. Assuming no 1485 ** error occurs the xInput method should copy up to (*pnData) bytes of data 1486 ** into the buffer and set (*pnData) to the actual number of bytes copied 1487 ** before returning SQLITE_OK. If the input is completely exhausted, (*pnData) 1488 ** should be set to zero to indicate this. Or, if an error occurs, an SQLite 1489 ** error code should be returned. In all cases, if an xInput callback returns 1490 ** an error, all processing is abandoned and the streaming API function 1491 ** returns a copy of the error code to the caller. 1492 ** 1493 ** In the case of sqlite3changeset_start_strm(), the xInput callback may be 1494 ** invoked by the sessions module at any point during the lifetime of the 1495 ** iterator. If such an xInput callback returns an error, the iterator enters 1496 ** an error state, whereby all subsequent calls to iterator functions 1497 ** immediately fail with the same error code as returned by xInput. 1498 ** 1499 ** Similarly, streaming API functions that return changesets (or patchsets) 1500 ** return them in chunks by way of a callback function instead of via a 1501 ** pointer to a single large buffer. In this case, a pair of parameters such 1502 ** as: 1503 ** 1504 ** <pre> 1505 ** int *pnChangeset, 1506 ** void **ppChangeset, 1507 ** </pre> 1508 ** 1509 ** Is replaced by: 1510 ** 1511 ** <pre> 1512 ** int (*xOutput)(void *pOut, const void *pData, int nData), 1513 ** void *pOut 1514 ** </pre> 1515 ** 1516 ** The xOutput callback is invoked zero or more times to return data to 1517 ** the application. The first parameter passed to each call is a copy of the 1518 ** pOut pointer supplied by the application. The second parameter, pData, 1519 ** points to a buffer nData bytes in size containing the chunk of output 1520 ** data being returned. If the xOutput callback successfully processes the 1521 ** supplied data, it should return SQLITE_OK to indicate success. Otherwise, 1522 ** it should return some other SQLite error code. In this case processing 1523 ** is immediately abandoned and the streaming API function returns a copy 1524 ** of the xOutput error code to the application. 1525 ** 1526 ** The sessions module never invokes an xOutput callback with the third 1527 ** parameter set to a value less than or equal to zero. Other than this, 1528 ** no guarantees are made as to the size of the chunks of data returned. 1529 */ 1530 int sqlite3changeset_apply_strm( 1531 sqlite3 *db, /* Apply change to "main" db of this handle */ 1532 int (*xInput)(void *pIn, void *pData, int *pnData), /* Input function */ 1533 void *pIn, /* First arg for xInput */ 1534 int(*xFilter)( 1535 void *pCtx, /* Copy of sixth arg to _apply() */ 1536 const char *zTab /* Table name */ 1537 ), 1538 int(*xConflict)( 1539 void *pCtx, /* Copy of sixth arg to _apply() */ 1540 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 1541 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 1542 ), 1543 void *pCtx /* First argument passed to xConflict */ 1544 ); 1545 int sqlite3changeset_apply_v2_strm( 1546 sqlite3 *db, /* Apply change to "main" db of this handle */ 1547 int (*xInput)(void *pIn, void *pData, int *pnData), /* Input function */ 1548 void *pIn, /* First arg for xInput */ 1549 int(*xFilter)( 1550 void *pCtx, /* Copy of sixth arg to _apply() */ 1551 const char *zTab /* Table name */ 1552 ), 1553 int(*xConflict)( 1554 void *pCtx, /* Copy of sixth arg to _apply() */ 1555 int eConflict, /* DATA, MISSING, CONFLICT, CONSTRAINT */ 1556 sqlite3_changeset_iter *p /* Handle describing change and conflict */ 1557 ), 1558 void *pCtx, /* First argument passed to xConflict */ 1559 void **ppRebase, int *pnRebase, 1560 int flags 1561 ); 1562 int sqlite3changeset_concat_strm( 1563 int (*xInputA)(void *pIn, void *pData, int *pnData), 1564 void *pInA, 1565 int (*xInputB)(void *pIn, void *pData, int *pnData), 1566 void *pInB, 1567 int (*xOutput)(void *pOut, const void *pData, int nData), 1568 void *pOut 1569 ); 1570 int sqlite3changeset_invert_strm( 1571 int (*xInput)(void *pIn, void *pData, int *pnData), 1572 void *pIn, 1573 int (*xOutput)(void *pOut, const void *pData, int nData), 1574 void *pOut 1575 ); 1576 int sqlite3changeset_start_strm( 1577 sqlite3_changeset_iter **pp, 1578 int (*xInput)(void *pIn, void *pData, int *pnData), 1579 void *pIn 1580 ); 1581 int sqlite3changeset_start_v2_strm( 1582 sqlite3_changeset_iter **pp, 1583 int (*xInput)(void *pIn, void *pData, int *pnData), 1584 void *pIn, 1585 int flags 1586 ); 1587 int sqlite3session_changeset_strm( 1588 sqlite3_session *pSession, 1589 int (*xOutput)(void *pOut, const void *pData, int nData), 1590 void *pOut 1591 ); 1592 int sqlite3session_patchset_strm( 1593 sqlite3_session *pSession, 1594 int (*xOutput)(void *pOut, const void *pData, int nData), 1595 void *pOut 1596 ); 1597 int sqlite3changegroup_add_strm(sqlite3_changegroup*, 1598 int (*xInput)(void *pIn, void *pData, int *pnData), 1599 void *pIn 1600 ); 1601 int sqlite3changegroup_output_strm(sqlite3_changegroup*, 1602 int (*xOutput)(void *pOut, const void *pData, int nData), 1603 void *pOut 1604 ); 1605 int sqlite3rebaser_rebase_strm( 1606 sqlite3_rebaser *pRebaser, 1607 int (*xInput)(void *pIn, void *pData, int *pnData), 1608 void *pIn, 1609 int (*xOutput)(void *pOut, const void *pData, int nData), 1610 void *pOut 1611 ); 1612 1613 /* 1614 ** CAPI3REF: Configure global parameters 1615 ** 1616 ** The sqlite3session_config() interface is used to make global configuration 1617 ** changes to the sessions module in order to tune it to the specific needs 1618 ** of the application. 1619 ** 1620 ** The sqlite3session_config() interface is not threadsafe. If it is invoked 1621 ** while any other thread is inside any other sessions method then the 1622 ** results are undefined. Furthermore, if it is invoked after any sessions 1623 ** related objects have been created, the results are also undefined. 1624 ** 1625 ** The first argument to the sqlite3session_config() function must be one 1626 ** of the SQLITE_SESSION_CONFIG_XXX constants defined below. The 1627 ** interpretation of the (void*) value passed as the second parameter and 1628 ** the effect of calling this function depends on the value of the first 1629 ** parameter. 1630 ** 1631 ** <dl> 1632 ** <dt>SQLITE_SESSION_CONFIG_STRMSIZE<dd> 1633 ** By default, the sessions module streaming interfaces attempt to input 1634 ** and output data in approximately 1 KiB chunks. This operand may be used 1635 ** to set and query the value of this configuration setting. The pointer 1636 ** passed as the second argument must point to a value of type (int). 1637 ** If this value is greater than 0, it is used as the new streaming data 1638 ** chunk size for both input and output. Before returning, the (int) value 1639 ** pointed to by pArg is set to the final value of the streaming interface 1640 ** chunk size. 1641 ** </dl> 1642 ** 1643 ** This function returns SQLITE_OK if successful, or an SQLite error code 1644 ** otherwise. 1645 */ 1646 int sqlite3session_config(int op, void *pArg); 1647 1648 /* 1649 ** CAPI3REF: Values for sqlite3session_config(). 1650 */ 1651 #define SQLITE_SESSION_CONFIG_STRMSIZE 1 1652 1653 /* 1654 ** Make sure we can call this stuff from C++. 1655 */ 1656 #ifdef __cplusplus 1657 } 1658 #endif 1659 1660 #endif /* !defined(__SQLITESESSION_H_) && defined(SQLITE_ENABLE_SESSION) */ 1661