Lines Matching full:sql
253 ** SQL statements without having to write a lot of C code. The UTF-8 encoded
254 ** SQL statements are passed in as the second parameter to sqlite3_exec().
258 ** results produced by the SQL statements. The 5th parameter tells where
267 ** If the SQL statement in the 2nd parameter is NULL or an empty string
268 ** or a string containing only whitespace and comments, then no SQL
286 ** The SQL statement text in the 2nd parameter to [sqlite3_exec()]
295 const char *sql, /* SQL to be evaluated */
315 #define SQLITE_ERROR 1 /* SQL error or missing database */
1215 ** or inserted or deleted by the most recently completed SQL statement
1229 ** ends with the script of a trigger. Most SQL statements are
1319 ** If an SQL operation is very nearly finished at the time when
1323 ** An SQL operation that is interrupted will return [SQLITE_INTERRUPT].
1324 ** If the interrupted SQL operation is an INSERT, UPDATE, or DELETE
1328 ** A call to sqlite3_interrupt() has no effect on SQL statements
1340 ** CAPI3REF: Determine If An SQL Statement Is Complete {H10510} <S70200>
1343 ** currently entered text seems to form complete a SQL statement or
1346 ** appears to be a complete SQL statement. A statement is judged to be
1353 ** These routines do not parse the SQL statements thus
1354 ** will not detect syntactically incorrect SQL.
1364 int sqlite3_complete(const char *sql);
1365 int sqlite3_complete16(const void *sql);
1509 ** semicolon-separated SQL statements in the zero-terminated UTF-8
1532 const char *zSql, /* SQL to be evaluated */
1573 ** options that are useful for constructing SQL statements.
1589 ** One can use this text in an SQL statement as follows:
1598 ** is escaped and the SQL generated is as follows:
1604 ** This is correct. Had we used %s instead of %q, the generated SQL
1611 ** This second example is an SQL syntax error. As a general rule you should
1625 ** The code above will render a correct SQL statement in the zSQL
1743 ** the build-in random() and randomblob() SQL functions. This interface allows
1765 ** The authorizer callback is invoked as SQL statements are being compiled
1772 ** specific action but allow the SQL statement to continue to be
1773 ** compiled, or [SQLITE_DENY] to cause the entire SQL statement to be
1799 ** SQL statements from an untrusted source, to ensure that the SQL statements
1803 ** SQL queries for evaluation by a database. But the application does
1806 ** user-entered SQL is being [sqlite3_prepare | prepared] that
1809 ** Applications that need to process SQL from untrusted sources
1852 #define SQLITE_DENY 1 /* Abort the SQL statement with an error */
1859 ** that is invoked to authorize certain SQL statement actions. The
1872 ** top-level SQL code.
1917 ** tracing and profiling the execution of SQL statements.
1920 ** various times when an SQL statement is being run by [sqlite3_step()].
1921 ** The callback returns a UTF-8 rendering of the SQL statement text
1924 ** contain a UTF-8 SQL comment that identifies the trigger.
1927 ** as each SQL statement finishes. The profile callback contains
2104 ** CAPI3REF: SQL Statement Object {H13000} <H13010>
2107 ** An instance of this object represents a single SQL statement.
2109 ** "compiled SQL statement" or simply as a "statement".
2118 ** <li> Run the SQL
2157 ** interface to further control untrusted SQL. The size of the database
2182 ** <dd>The maximum length of an SQL statement.</dd>
2197 ** used to implement an SQL statement.</dd>
2210 ** <dd>The maximum number of variables in an SQL statement that can
2226 ** CAPI3REF: Compiling An SQL Statement {H13010} <S10000>
2227 ** KEYWORDS: {SQL statement compiler}
2229 ** To execute an SQL query, it must first be compiled into a byte-code
2251 ** first SQL statement in zSql. These routines only compile the first
2257 ** to NULL. If the input text contains no SQL (if the input is an empty
2260 ** SQL statement using [sqlite3_finalize()] after it has finished with it.
2269 ** original SQL text. This causes the [sqlite3_step()] interface to
2275 ** always used to do, [sqlite3_step()] will automatically recompile the SQL
2300 const char *zSql, /* SQL statement, UTF-8 encoded */
2307 const char *zSql, /* SQL statement, UTF-8 encoded */
2314 const void *zSql, /* SQL statement, UTF-16 encoded */
2321 const void *zSql, /* SQL statement, UTF-16 encoded */
2328 ** CAPI3REF: Retrieving Statement SQL {H13100} <H13000>
2331 ** SQL text used to create a [prepared statement] if that statement was
2368 ** implementation of [application-defined SQL functions] are protected.
2379 ** CAPI3REF: SQL Function Context Object {H16001} <S20200>
2381 ** The context in which an SQL function executes is stored in an
2383 ** is always first parameter to [application-defined SQL functions].
2384 ** The application-defined SQL function implementation will pass this
2395 ** KEYWORDS: {SQL parameter} {SQL parameters} {parameter binding}
2397 ** In the SQL strings input to [sqlite3_prepare_v2()] and its variants,
2410 ** parameters (also called "host parameter names" or "SQL parameters")
2417 ** The second argument is the index of the SQL parameter to be set.
2418 ** The leftmost SQL parameter has an index of 1. When the same named
2419 ** SQL parameter is used more than once, second and subsequent
2487 ** CAPI3REF: Number Of SQL Parameters {H13600} <S70300>
2489 ** This routine can be used to find the number of [SQL parameters]
2490 ** in a [prepared statement]. SQL parameters are tokens of the
2513 ** [SQL parameter] in a [prepared statement].
2514 ** SQL parameters of the form "?NNN" or ":AAA" or "@AAA" or "$AAA"
2542 ** Return the index of an SQL parameter given its name. The
2574 ** [prepared statement]. This routine returns 0 if pStmt is an SQL
2700 ** CAPI3REF: Evaluate An SQL Statement {H13200} <S10000>
2731 ** If the SQL statement being executed returns any data, then [SQLITE_ROW]
2758 ** with the "v2" interface. If you prepare all of your SQL statements
2824 ** If the SQL statement does not currently point to a valid row, or if the
3004 ** Any SQL statement variables that had values bound to them using
3026 ** CAPI3REF: Create Or Redefine SQL Functions {H16100} <S20200>
3028 ** KEYWORDS: {application-defined SQL function}
3029 ** KEYWORDS: {application-defined SQL functions}
3032 ** are used to add SQL functions or aggregates or to redefine the behavior
3033 ** of existing SQL functions or aggregates. The only difference between the
3038 ** The first parameter is the [database connection] to which the SQL
3040 ** connection internally, then SQL functions must be added individually to
3043 ** The second parameter is the name of the SQL function to be created or
3050 ** is the number of arguments that the SQL function or
3051 ** aggregate takes. If this parameter is negative, then the SQL function or
3055 ** [SQLITE_UTF8 | text encoding] this SQL function prefers for
3056 ** its parameters. Any SQL function implementation should be able to work
3070 ** pointers to C-language functions that implement the SQL function or
3071 ** aggregate. A scalar SQL function requires an implementation of the xFunc
3073 ** parameters. An aggregate SQL function requires an implementation of xStep
3075 ** SQL function or aggregate, pass NULL for all three function callbacks.
3081 ** SQL function is used. A function implementation with a non-negative
3160 ** CAPI3REF: Obtaining SQL Function Parameter Values {H15100} <S20200>
3162 ** The C-language implementation of SQL functions and aggregates uses
3168 ** define callbacks that implement the SQL functions and aggregates.
3171 ** each parameter to the SQL function. These routines are used to
3202 ** the SQL function that supplied the [sqlite3_value*] parameters.
3224 ** The implementation of aggregate SQL functions use this routine to allocate
3238 ** [sqlite3_context | SQL function context] that is the first parameter
3242 ** the aggregate SQL function is running.
3283 ** The following two functions may be used by scalar SQL functions to
3285 ** multiple invocations of the same SQL function during query execution, under
3289 ** metadata associated with the SQL value passed as the regular expression
3309 ** or when the SQL statement completes, whichever comes first.
3317 ** values and SQL variables.
3320 ** the SQL function is running.
3348 ** CAPI3REF: Setting The Result Of An SQL Function {H16400} <S20200>
3351 ** implement SQL functions and aggregates. See
3357 ** Refer to the [SQL parameter] documentation for additional information.
3373 ** cause the implemented SQL function to throw an exception.
3979 ** extension loading while evaluating user-entered SQL, the following API
4754 ** <a href="lang_attach.html">ATTACH</a> SQL command that opened the
