Small. Fast. Reliable.
Choose any three.
Choose any three.
|
The ON CONFLICT Clause
(lang_conflict.html)
The ON CONFLICT clause is a
non-standard extension specific to SQLite
that can appear in many other SQL commands.
It is given its own section in this document because it is not
part of standard SQL and therefore might ...
|
|
C API: Conflict resolution modes
(c3ref/c_fail.html)
sqlite3_authorizer(), SQLITE_ROLLBACK, SQLITE_FAIL, SQLITE_ABORT, SQLITE_REPLACE
These constants are returned by sqlite3_vtab_on_conflict() to
inform a virtual table implementation what the ON CONFLICT mode
is for the SQL statement being evaluated.
Note that the SQLITE_IGNORE constant is also used as a potential
return value from the sqlite3_set_authorizer ...
|
|
C API: Determine The Virtual Table Conflict Policy
(c3ref/vtab_on_conflict.html)
sqlite3_vtab_on_conflict()
... The
value returned is one of SQLITE_ROLLBACK, SQLITE_IGNORE, SQLITE_FAIL,
SQLITE_ABORT, or SQLITE_REPLACE, according to the ON CONFLICT mode
of the SQL statement that triggered the call to the xUpdate method of the
virtual table.
See also lists of
Objects,
Constants ...
|
|
Constraint Conflict Resolution in SQLite
(conflict.html)
Constraint Conflict Resolution in SQLite
In most SQL databases, if you have a UNIQUE, NOT NULL, or
CHECK constraint on
a table and you try to do an UPDATE or INSERT that violates
the constraint, the database will abort the ...
|
|
UPSERT
(lang_upsert.html)
... If the last
ON CONFLICT clause omits the conflict target, then it will fire if any
uniqueness constraint fails which is not captured by prior ON CONFLICT clauses.
Only a single ON CONFLICT clause, specifically the first ON CONFLICT
clause ...
|
|
C API: Virtual Table Configuration Options
(c3ref/c_vtab_constraint_support.html)
SQLITE_VTAB_CONSTRAINT_SUPPORT, SQLITE_VTAB_INNOCUOUS, SQLITE_VTAB_DIRECTONLY, SQLITE_VTAB_USES_ALL_SCHEMAS
... If the ON CONFLICT mode is ABORT, FAIL, IGNORE or ROLLBACK, SQLite
is able to roll back a statement or database transaction, and abandon
or continue processing the current SQL statement as appropriate.
If the ON CONFLICT mode is REPLACE ...
|
|
SQLite Session Module C/C++ Interface
(session.html)
... 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 Session Extension
(sessionintro.html)
2.2. Conflicts
... Depending on the type of conflict, a sessions application has a variety
of configurable options for dealing with conflicts, ranging from omitting the
conflicting change, aborting the entire changeset application or applying
the change despite the conflict. For details, refer ...
|
|
Maintaining Private Branches Of SQLite
(privatebranch.html)
2. The Basic Idea
... In that case, the maintainer will
have to manually resolve the conflicts. Hopefully conflicts
will not come up that often. Conflicts are less likely to
occur when the private edits are kept to a minimum.
The cycle above can be ...
|
|
C API: Authorizer Return Codes
(c3ref/c_deny.html)
SQLITE_DENY, SQLITE_IGNORE
... either SQLITE_OK or one of these two constants in order
to signal SQLite whether or not the action is permitted. See the
authorizer documentation for additional
information.
Note that SQLITE_IGNORE is also used as a conflict resolution mode
returned from ...
|
Page generated by FTS5 in about 28.27 ms.