mirror of
https://github.com/sqlite/sqlite.git
synced 2025-08-01 06:27:03 +03:00
Fix error in a comment in sqlite3session.h. No changes to code.
FossilOrigin-Name: 70c84e50209722a61d66fd737e42d49275745b62
This commit is contained in:
@ -296,12 +296,13 @@ int sqlite3session_isempty(sqlite3_session *pSession);
|
||||
**
|
||||
** Assuming the changeset blob was created by one of the
|
||||
** [sqlite3session_changeset()], [sqlite3changeset_concat()] or
|
||||
** [sqlite3changest_invert()], all changes within the changeset that apply
|
||||
** to a single table are grouped together. This means that when an application
|
||||
** iterates through a changeset using an iterator created by this function,
|
||||
** all changes that relate to a single table are visted consecutively. There
|
||||
** is no chance that the iterator will visit a change the applies to table X,
|
||||
** then one for table Y, and then later on visit another change for table X.
|
||||
** [sqlite3changeset_invert()] functions, all changes within the changeset
|
||||
** that apply to a single table are grouped together. This means that when
|
||||
** an application iterates through a changeset using an iterator created by
|
||||
** this function, all changes that relate to a single table are visted
|
||||
** consecutively. There is no chance that the iterator will visit a change
|
||||
** the applies to table X, then one for table Y, and then later on visit
|
||||
** another change for table X.
|
||||
*/
|
||||
int sqlite3changeset_start(
|
||||
sqlite3_changeset_iter **pp, /* OUT: New changeset iterator handle */
|
||||
|
Reference in New Issue
Block a user