summaryrefslogtreecommitdiff
path: root/static/netbsd/man3/sqlite3_stmt.3
diff options
context:
space:
mode:
Diffstat (limited to 'static/netbsd/man3/sqlite3_stmt.3')
-rw-r--r--static/netbsd/man3/sqlite3_stmt.351
1 files changed, 51 insertions, 0 deletions
diff --git a/static/netbsd/man3/sqlite3_stmt.3 b/static/netbsd/man3/sqlite3_stmt.3
new file mode 100644
index 00000000..0465eecf
--- /dev/null
+++ b/static/netbsd/man3/sqlite3_stmt.3
@@ -0,0 +1,51 @@
+.Dd January 24, 2024
+.Dt SQLITE3_STMT 3
+.Os
+.Sh NAME
+.Nm sqlite3_stmt
+.Nd prepared statement object
+.Sh SYNOPSIS
+.In sqlite3.h
+.Vt typedef struct sqlite3_stmt sqlite3_stmt;
+.Sh DESCRIPTION
+An instance of this object represents a single SQL statement that has
+been compiled into binary form and is ready to be evaluated.
+.Pp
+Think of each SQL statement as a separate computer program.
+The original SQL text is source code.
+A prepared statement object is the compiled object code.
+All SQL must be converted into a prepared statement before it can be
+run.
+.Pp
+The life-cycle of a prepared statement object usually goes like this:
+.Bl -enum
+.It
+Create the prepared statement object using
+.Fn sqlite3_prepare_v2 .
+.It
+Bind values to parameters using the sqlite3_bind_*() interfaces.
+.It
+Run the SQL by calling
+.Fn sqlite3_step
+one or more times.
+.It
+Reset the prepared statement using
+.Fn sqlite3_reset
+then go back to step 2.
+Do this zero or more times.
+.It
+Destroy the object using
+.Fn sqlite3_finalize .
+.El
+.Pp
+.Sh IMPLEMENTATION NOTES
+These declarations were extracted from the
+interface documentation at line 4000.
+.Bd -literal
+typedef struct sqlite3_stmt sqlite3_stmt;
+.Ed
+.Sh SEE ALSO
+.Xr sqlite3_finalize 3 ,
+.Xr sqlite3_prepare 3 ,
+.Xr sqlite3_reset 3 ,
+.Xr sqlite3_step 3