From 63847496f14c813a5d80efd5b7de0f1294ffe1e3 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 13 Apr 2024 16:07:11 +0200 Subject: Adding upstream version 3.45.1. Signed-off-by: Daniel Baumann --- www/session/c_changesetapply_fknoaction.html | 163 +++++++++++++++++++++++++++ 1 file changed, 163 insertions(+) create mode 100644 www/session/c_changesetapply_fknoaction.html (limited to 'www/session/c_changesetapply_fknoaction.html') diff --git a/www/session/c_changesetapply_fknoaction.html b/www/session/c_changesetapply_fknoaction.html new file mode 100644 index 0000000..779c6e4 --- /dev/null +++ b/www/session/c_changesetapply_fknoaction.html @@ -0,0 +1,163 @@ + + + + + +Flags for sqlite3changeset_apply_v2 + + + +
+ + + +
+
+Small. Fast. Reliable.
Choose any three. +
+
+ +
+ +
+
+ + + +
+
+
+ +

Session Module C Interface

Flags for sqlite3changeset_apply_v2

#define SQLITE_CHANGESETAPPLY_NOSAVEPOINT   0x0001
+#define SQLITE_CHANGESETAPPLY_INVERT        0x0002
+#define SQLITE_CHANGESETAPPLY_IGNORENOOP    0x0004
+#define SQLITE_CHANGESETAPPLY_FKNOACTION    0x0008
+

+The following flags may passed via the 9th parameter to +sqlite3changeset_apply_v2 and sqlite3changeset_apply_v2_strm:

+ +

+
SQLITE_CHANGESETAPPLY_NOSAVEPOINT
+ Usually, the sessions module encloses all operations performed by + a single call to apply_v2() or apply_v2_strm() in a SAVEPOINT. The + SAVEPOINT is committed if the changeset or patchset is successfully + applied, or rolled back if an error occurs. Specifying this flag + causes the sessions module to omit this savepoint. In this case, if the + caller has an open transaction or savepoint when apply_v2() is called, + it may revert the partially applied changeset by rolling it back.

+ +

SQLITE_CHANGESETAPPLY_INVERT
+ Invert the changeset before applying it. This is equivalent to inverting + a changeset using sqlite3changeset_invert() before applying it. It is + an error to specify this flag with a patchset.

+ +

SQLITE_CHANGESETAPPLY_IGNORENOOP
+ Do not invoke the conflict handler callback for any changes that + would not actually modify the database even if they were applied. + Specifically, this means that the conflict handler is not invoked + for: +
    +
  • a delete change if the row being deleted cannot be found, +
  • an update change if the modified fields are already set to + their new values in the conflicting row, or +
  • an insert change if all fields of the conflicting row match + the row being inserted. +

+ +

SQLITE_CHANGESETAPPLY_FKNOACTION
+ If this flag it set, then all foreign key constraints in the target + database behave as if they were declared with "ON UPDATE NO ACTION ON + DELETE NO ACTION", even if they are actually CASCADE, RESTRICT, SET NULL + or SET DEFAULT. +

See also lists of + Objects, + Constants, and + Functions.

+ -- cgit v1.2.3