summaryrefslogtreecommitdiff
path: root/static/netbsd/man3/sqlite3session_isempty.3
diff options
context:
space:
mode:
Diffstat (limited to 'static/netbsd/man3/sqlite3session_isempty.3')
-rw-r--r--static/netbsd/man3/sqlite3session_isempty.334
1 files changed, 34 insertions, 0 deletions
diff --git a/static/netbsd/man3/sqlite3session_isempty.3 b/static/netbsd/man3/sqlite3session_isempty.3
new file mode 100644
index 00000000..ccd21882
--- /dev/null
+++ b/static/netbsd/man3/sqlite3session_isempty.3
@@ -0,0 +1,34 @@
+.Dd January 24, 2024
+.Dt SQLITE3SESSION_ISEMPTY 3
+.Os
+.Sh NAME
+.Nm sqlite3session_isempty
+.Nd test if a changeset has recorded any changes
+.Sh SYNOPSIS
+.In sqlite3.h
+.Ft int
+.Fo sqlite3session_isempty
+.Fa "sqlite3_session *pSession"
+.Fc
+.Sh DESCRIPTION
+Return non-zero if no changes to attached tables have been recorded
+by the session object passed as the first argument.
+Otherwise, if one or more changes have been recorded, return zero.
+.Pp
+Even if this function returns zero, it is possible that calling
+.Fn sqlite3session_changeset
+on the session handle may still return a changeset that contains no
+changes.
+This can happen when a row in an attached table is modified and then
+later on the original values are restored.
+However, if this function returns non-zero, then it is guaranteed that
+a call to sqlite3session_changeset() will return a changeset containing
+zero changes.
+.Sh IMPLEMENTATION NOTES
+These declarations were extracted from the
+interface documentation at line 11410.
+.Bd -literal
+SQLITE_API int sqlite3session_isempty(sqlite3_session *pSession);
+.Ed
+.Sh SEE ALSO
+.Xr sqlite3session_changeset 3