Abort when a change encounters a conflict and roll back database.
namespace
sqlite.constants
namespace constants
- const SQLITE_CHANGESET_CONFLICT: number
This constant is passed to the conflict handler while processing an INSERT change if the operation would result in duplicate primary key values.
- const SQLITE_CHANGESET_DATA: number
The conflict handler is invoked with this constant when processing a DELETE or UPDATE change if a row with the required PRIMARY KEY fields is present in the database, but one or more other (non primary-key) fields modified by the update do not contain the expected "before" values.
- const SQLITE_CHANGESET_FOREIGN_KEY: number
If foreign key handling is enabled, and applying a changeset leaves the database in a state containing foreign key violations, the conflict handler is invoked with this constant exactly once before the changeset is committed. If the conflict handler returns
SQLITE_CHANGESET_OMIT, the changes, including those that caused the foreign key constraint violation, are committed. Or, if it returnsSQLITE_CHANGESET_ABORT, the changeset is rolled back. - const SQLITE_CHANGESET_NOTFOUND: number
The conflict handler is invoked with this constant when processing a DELETE or UPDATE change if a row with the required PRIMARY KEY fields is not present in the database.
- const SQLITE_CHANGESET_REPLACE: number
Conflicting changes replace existing values. Note that this value can only be returned when the type of conflict is either
SQLITE_CHANGESET_DATAorSQLITE_CHANGESET_CONFLICT.