Updated: 2025/Nov/16
Please read Privacy Policy. It's for your privacy.
SQLITE_CHANGESET_OMIT(3) Library Functions Manual SQLITE_CHANGESET_OMIT(3)
NAME
SQLITE_CHANGESET_OMIT, SQLITE_CHANGESET_REPLACE, SQLITE_CHANGESET_ABORT -
constants returned by the conflict handler
SYNOPSIS
#include <sqlite3.h>
#define SQLITE_CHANGESET_OMIT
#define SQLITE_CHANGESET_REPLACE
#define SQLITE_CHANGESET_ABORT
DESCRIPTION
A conflict handler callback must return one of the following three
values.
SQLITE_CHANGESET_OMIT
If a conflict handler returns this value no special action is
taken. The change that caused the conflict is not applied. The
session module continues to the next change in the changeset.
SQLITE_CHANGESET_REPLACE
This value may only be returned if the second argument to the
conflict handler was SQLITE_CHANGESET_DATA or
SQLITE_CHANGESET_CONFLICT. If this is not the case, any changes
applied so far are rolled back and the call to
sqlite3changeset_apply() returns SQLITE_MISUSE.
If CHANGESET_REPLACE is returned by an SQLITE_CHANGESET_DATA
conflict handler, then the conflicting row is either updated or
deleted, depending on the type of change.
If CHANGESET_REPLACE is returned by an SQLITE_CHANGESET_CONFLICT
conflict handler, then the conflicting row is removed from the
database and a second attempt to apply the change is made. If
this second attempt fails, the original row is restored to the
database before continuing.
SQLITE_CHANGESET_ABORT
If this value is returned, any changes applied so far are rolled
back and the call to sqlite3changeset_apply() returns
SQLITE_ABORT.
IMPLEMENTATION NOTES
These declarations were extracted from the interface documentation at
line 12317.
#define SQLITE_CHANGESET_OMIT 0
#define SQLITE_CHANGESET_REPLACE 1
#define SQLITE_CHANGESET_ABORT 2
NetBSD 11.99 January 24, 2024 NetBSD 11.99