Constants6
[<Interface>]
type Constants6 =
abstract member SQLITE_CHANGESET_ABORT: float
abstract member SQLITE_CHANGESET_CONFLICT: float
abstract member SQLITE_CHANGESET_DATA: float
abstract member SQLITE_CHANGESET_FOREIGN_KEY: float
abstract member SQLITE_CHANGESET_NOTFOUND: float
abstract member SQLITE_CHANGESET_OMIT: float
abstract member SQLITE_CHANGESET_REPLACE: float
static member Create (SQLITE_CHANGESET_DATA: float, SQLITE_CHANGESET_NOTFOUND: float, SQLITE_CHANGESET_CONFLICT: float, SQLITE_CHANGESET_FOREIGN_KEY: float, SQLITE_CHANGESET_OMIT: float, SQLITE_CHANGESET_REPLACE: float, SQLITE_CHANGESET_ABORT: float) : Constants6| Assembly | Xantham.Fable.Node |
| Attributes | [<Interface>] |
Properties
abstract member SQLITE_CHANGESET_ABORT: float
abstract member SQLITE_CHANGESET_ABORT: floatAbort when a change encounters a conflict and roll back database.
@since v22.12.0
abstract member SQLITE_CHANGESET_CONFLICT: float
abstract member SQLITE_CHANGESET_CONFLICT: floatThis constant is passed to the conflict handler while processing an INSERT change if the operation would result in duplicate primary key values.
@since v22.14.0
abstract member SQLITE_CHANGESET_DATA: float
abstract member SQLITE_CHANGESET_DATA: floatThe 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.
@since v22.14.0
abstract member SQLITE_CHANGESET_FOREIGN_KEY: float
abstract member SQLITE_CHANGESET_FOREIGN_KEY: floatIf 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 returns SQLITE_CHANGESET_ABORT, the changeset is rolled back.
@since v22.14.0
abstract member SQLITE_CHANGESET_NOTFOUND: float
abstract member SQLITE_CHANGESET_NOTFOUND: floatThe 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.
@since v22.14.0
abstract member SQLITE_CHANGESET_REPLACE: float
abstract member SQLITE_CHANGESET_REPLACE: floatConflicting changes replace existing values. Note that this value can only be returned when the type of conflict is either SQLITE_CHANGESET_DATA or SQLITE_CHANGESET_CONFLICT.
@since v22.12.0
Methods
static member Create (SQLITE_CHANGESET_DATA: float, SQLITE_CHANGESET_NOTFOUND: float, SQLITE_CHANGESET_CONFLICT: float, SQLITE_CHANGESET_FOREIGN_KEY: float, SQLITE_CHANGESET_OMIT: float, SQLITE_CHANGESET_REPLACE: float, SQLITE_CHANGESET_ABORT: float) : Constants6