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/c3ref/log.html | 148 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 148 insertions(+) create mode 100644 www/c3ref/log.html (limited to 'www/c3ref/log.html') diff --git a/www/c3ref/log.html b/www/c3ref/log.html new file mode 100644 index 0000000..1b1f5e8 --- /dev/null +++ b/www/c3ref/log.html @@ -0,0 +1,148 @@ + + + + + +Error Logging Interface + + + +
+ + + +
+
+Small. Fast. Reliable.
Choose any three. +
+
+ +
+ +
+
+ + + +
+
+
+ + +
+

SQLite C Interface

 +

Error Logging Interface

+
+
+void sqlite3_log(int iErrCode, const char *zFormat, ...);
+
+

+The sqlite3_log() interface writes a message into the error log +established by the SQLITE_CONFIG_LOG option to sqlite3_config(). +If logging is enabled, the zFormat string and subsequent arguments are +used with sqlite3_snprintf() to generate the final output string.

+ +

The sqlite3_log() interface is intended for use by extensions such as +virtual tables, collating functions, and SQL functions. While there is +nothing to prevent an application from calling sqlite3_log(), doing so +is considered bad form.

+ +

The zFormat string must not be NULL.

+ +

To avoid deadlocks and other threading problems, the sqlite3_log() routine +will not use dynamically allocated memory. The log message is stored in +a fixed-length buffer on the stack. If the log message is longer than +a few hundred characters, it will be truncated to the length of the +buffer. +

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

+ -- cgit v1.2.3