Lines Matching full:sql
168 ** See also: SQL functions [sqlite_compileoption_used()] and
304 ** that allows an application to run multiple statements of SQL
308 ** semicolon-separate SQL statements passed into its 2nd argument,
312 ** coming out of the evaluated SQL statements. ^The 4th argument to
318 ** ^If an error occurs while evaluating the SQL statements passed into
332 ** without running any subsequent SQL statements.
346 ** SQL comments, then no SQL statements are evaluated and the database
356 ** <li> The application must not modify the SQL statement text passed into
362 const char *sql, /* SQL to be evaluated */
382 #define SQLITE_ERROR 1 /* SQL error or missing database */
1497 ** This function is accessible to SQL statements via the
1498 ** [last_insert_rowid() SQL function].
1513 ** or inserted or deleted by the most recently completed SQL statement
1532 ** Most SQL statements are
1555 ** [count_changes pragma], and the [changes() SQL function].
1581 ** [count_changes pragma], and the [total_changes() SQL function].
1603 ** ^If an SQL operation is very nearly finished at the time when
1607 ** ^An SQL operation that is interrupted will return [SQLITE_INTERRUPT].
1608 ** ^If the interrupted SQL operation is an INSERT, UPDATE, or DELETE
1613 ** SQL statements on [database connection] D complete. ^Any new SQL statements
1616 ** running prior to the sqlite3_interrupt() call. ^New SQL statements
1620 ** SQL statements is a no-op and has no effect on SQL statements
1629 ** CAPI3REF: Determine If An SQL Statement Is Complete
1632 ** currently entered text seems to form a complete SQL statement or
1635 ** appears to be a complete SQL statement. ^A statement is judged to be
1646 ** ^These routines do not parse the SQL statements thus
1647 ** will not detect syntactically incorrect SQL.
1653 ** regardless of whether or not the input SQL is complete.)^
1661 SQLITE_API int sqlite3_complete(const char *sql);
1662 SQLITE_API int sqlite3_complete16(const void *sql);
1803 ** semicolon-separated SQL statements in the zero-terminated UTF-8
1824 const char *zSql, /* SQL to be evaluated */
1865 ** options that are useful for constructing SQL statements.
1881 ** One can use this text in an SQL statement as follows:
1890 ** is escaped and the SQL generated is as follows:
1896 ** This is correct. Had we used %s instead of %q, the generated SQL
1903 ** This second example is an SQL syntax error. As a general rule you should
1917 ** The code above will render a correct SQL statement in the zSQL
2034 ** the build-in random() and randomblob() SQL functions. This interface allows
2053 ** ^The authorizer callback is invoked as SQL statements are being compiled
2060 ** specific action but allow the SQL statement to continue to be
2061 ** compiled, or [SQLITE_DENY] to cause the entire SQL statement to be
2092 ** SQL statements from an untrusted source, to ensure that the SQL statements
2096 ** SQL queries for evaluation by a database. But the application does
2099 ** user-entered SQL is being [sqlite3_prepare | prepared] that
2102 ** Applications that need to process SQL from untrusted sources
2143 #define SQLITE_DENY 1 /* Abort the SQL statement with an error */
2150 ** that is invoked to authorize certain SQL statement actions. The
2163 ** top-level SQL code.
2204 ** tracing and profiling the execution of SQL statements.
2207 ** various times when an SQL statement is being run by [sqlite3_step()].
2209 ** SQL statement text as the statement first begins executing.
2212 ** contain a UTF-8 SQL comment that identifies the trigger.)^
2215 ** as each SQL statement finishes. ^The profile callback contains
2404 ** CAPI3REF: SQL Statement Object
2407 ** An instance of this object represents a single SQL statement.
2409 ** "compiled SQL statement" or simply as a "statement".
2418 ** <li> Run the SQL by calling [sqlite3_step()] one or more times.
2462 ** interface to further control untrusted SQL. The size of the database
2484 ** <dd>The maximum length of an SQL statement, in bytes.</dd>)^
2499 ** used to implement an SQL statement. This limit is not currently
2514 ** <dd>The maximum index number of any [parameter] in an SQL statement.)^
2533 ** CAPI3REF: Compiling An SQL Statement
2534 ** KEYWORDS: {SQL statement compiler}
2536 ** To execute an SQL query, it must first be compiled into a byte-code
2559 ** past the end of the first SQL statement in zSql. These routines only
2565 ** to NULL. ^If the input text contains no SQL (if the input is an empty
2568 ** SQL statement using [sqlite3_finalize()] after it has finished with it.
2579 ** original SQL text. This causes the [sqlite3_step()] interface to
2585 ** always used to do, [sqlite3_step()] will automatically recompile the SQL
2614 const char *zSql, /* SQL statement, UTF-8 encoded */
2621 const char *zSql, /* SQL statement, UTF-8 encoded */
2628 const void *zSql, /* SQL statement, UTF-16 encoded */
2635 const void *zSql, /* SQL statement, UTF-16 encoded */
2642 ** CAPI3REF: Retrieving Statement SQL
2645 ** SQL text used to create a [prepared statement] if that statement was
2651 ** CAPI3REF: Determine If An SQL Statement Writes The Database
2693 ** implementation of [application-defined SQL functions] are protected.
2704 ** CAPI3REF: SQL Function Context Object
2706 ** The context in which an SQL function executes is stored in an
2708 ** is always first parameter to [application-defined SQL functions].
2709 ** The application-defined SQL function implementation will pass this
2720 ** KEYWORDS: {SQL parameter} {SQL parameters} {parameter binding}
2722 ** ^(In the SQL statement text input to [sqlite3_prepare_v2()] and its variants,
2736 ** parameters (also called "host parameter names" or "SQL parameters")
2743 ** ^The second argument is the index of the SQL parameter to be set.
2744 ** ^The leftmost SQL parameter has an index of 1. ^When the same named
2745 ** SQL parameter is used more than once, second and subsequent
2810 ** CAPI3REF: Number Of SQL Parameters
2812 ** ^This routine can be used to find the number of [SQL parameters]
2813 ** in a [prepared statement]. SQL parameters are tokens of the
2833 ** the name of the N-th [SQL parameter] in the [prepared statement] P.
2834 ** ^(SQL parameters of the form "?NNN" or ":AAA" or "@AAA" or "$AAA"
2859 ** ^Return the index of an SQL parameter given its name. ^The
2885 ** [prepared statement]. ^This routine returns 0 if pStmt is an SQL
3002 ** CAPI3REF: Evaluate An SQL Statement
3033 ** ^If the SQL statement being executed returns any data, then [SQLITE_ROW]
3068 ** with the "v2" interface. If you prepare all of your SQL statements
3137 ** If the SQL statement does not currently point to a valid row, or if the
3327 ** ^Any SQL statement variables that had values bound to them using
3349 ** CAPI3REF: Create Or Redefine SQL Functions
3351 ** KEYWORDS: {application-defined SQL function}
3352 ** KEYWORDS: {application-defined SQL functions}
3355 ** are used to add SQL functions or aggregates or to redefine the behavior
3356 ** of existing SQL functions or aggregates. The only differences between
3362 ** ^The first parameter is the [database connection] to which the SQL
3364 ** connection then application-defined SQL functions must be added
3367 ** ^The second parameter is the name of the SQL function to be created or
3375 ** is the number of arguments that the SQL function or
3376 ** aggregate takes. ^If this parameter is -1, then the SQL function or
3383 ** [SQLITE_UTF8 | text encoding] this SQL function prefers for
3384 ** its parameters. Every SQL function implementation must be able to work
3398 ** pointers to C-language functions that implement the SQL function or
3399 ** aggregate. ^A scalar SQL function requires an implementation of the xFunc
3401 ** parameters. ^An aggregate SQL
3403 ** SQL function or aggregate, pass NULL poiners for all three function
3420 ** SQL function is used. ^A function implementation with a non-negative
3501 ** CAPI3REF: Obtaining SQL Function Parameter Values
3503 ** The C-language implementation of SQL functions and aggregates uses
3509 ** define callbacks that implement the SQL functions and aggregates.
3512 ** each parameter to the SQL function. These routines are used to
3543 ** the SQL function that supplied the [sqlite3_value*] parameters.
3561 ** Implementations of aggregate SQL functions use this
3590 ** [sqlite3_context | SQL function context] that is the first parameter
3595 ** the aggregate SQL function is running.
3627 ** The following two functions may be used by scalar SQL functions to
3629 ** multiple invocations of the same SQL function during query execution, under
3633 ** metadata associated with the SQL value passed as the regular expression
3653 ** or when the SQL statement completes, whichever comes first.
3664 ** the SQL function is running.
3689 ** CAPI3REF: Setting The Result Of An SQL Function
3692 ** implement SQL functions and aggregates. See
3698 ** Refer to the [SQL parameter] documentation for additional information.
3714 ** cause the implemented SQL function to throw an exception.
4396 ** See also the [load_extension() SQL function].
4410 ** extension loading while evaluating user-entered SQL, the following API
4805 ** interface. Use the [UPDATE] SQL command to change the size of a
4809 ** and the built-in [zeroblob] SQL function can be used, if desired,
5259 ** databases that are added using the [ATTACH] SQL command.
6091 ** virtual tables, collating functions, and SQL functions. While there is
6163 ** from SQL.
6182 ** from SQL. ^The [sqlite3_wal_autocheckpoint()] interface and the
6245 double *aParam; /* Parameters passed to SQL geom function */
