mirror of
https://github.com/sqlite/sqlite.git
synced 2025-11-22 20:22:44 +03:00
Add a C-source spell-checking facility. make misspell (on Nix)
FossilOrigin-Name: 26c1bb4bd9e9f56613c3aa87407a7f562fd4ebde5bfd6dece02078001d9a45f8
This commit is contained in:
@@ -9,7 +9,7 @@
|
||||
** May you share freely, never taking more than you give.
|
||||
**
|
||||
*************************************************************************
|
||||
**
|
||||
**
|
||||
** This file defines various limits of what SQLite can process.
|
||||
*/
|
||||
|
||||
@@ -57,9 +57,9 @@
|
||||
#endif
|
||||
|
||||
/*
|
||||
** The maximum depth of an expression tree. This is limited to
|
||||
** some extent by SQLITE_MAX_SQL_LENGTH. But sometime you might
|
||||
** want to place more severe limits on the complexity of an
|
||||
** The maximum depth of an expression tree. This is limited to
|
||||
** some extent by SQLITE_MAX_SQL_LENGTH. But sometime you might
|
||||
** want to place more severe limits on the complexity of an
|
||||
** expression. A value of 0 means that there is no limit.
|
||||
*/
|
||||
#ifndef SQLITE_MAX_EXPR_DEPTH
|
||||
@@ -72,7 +72,7 @@
|
||||
** level of recursion for each term. A stack overflow can result
|
||||
** if the number of terms is too large. In practice, most SQL
|
||||
** never has more than 3 or 4 terms. Use a value of 0 to disable
|
||||
** any limit on the number of terms in a compount SELECT.
|
||||
** any limit on the number of terms in a compound SELECT.
|
||||
*/
|
||||
#ifndef SQLITE_MAX_COMPOUND_SELECT
|
||||
# define SQLITE_MAX_COMPOUND_SELECT 500
|
||||
@@ -140,10 +140,10 @@
|
||||
**
|
||||
** Earlier versions of SQLite allowed the user to change this value at
|
||||
** compile time. This is no longer permitted, on the grounds that it creates
|
||||
** a library that is technically incompatible with an SQLite library
|
||||
** compiled with a different limit. If a process operating on a database
|
||||
** with a page-size of 65536 bytes crashes, then an instance of SQLite
|
||||
** compiled with the default page-size limit will not be able to rollback
|
||||
** a library that is technically incompatible with an SQLite library
|
||||
** compiled with a different limit. If a process operating on a database
|
||||
** with a page-size of 65536 bytes crashes, then an instance of SQLite
|
||||
** compiled with the default page-size limit will not be able to rollback
|
||||
** the aborted transaction. This could lead to database corruption.
|
||||
*/
|
||||
#ifdef SQLITE_MAX_PAGE_SIZE
|
||||
@@ -202,7 +202,7 @@
|
||||
** Maximum depth of recursion for triggers.
|
||||
**
|
||||
** A value of 1 means that a trigger program will not be able to itself
|
||||
** fire any triggers. A value of 0 means that no trigger programs at all
|
||||
** fire any triggers. A value of 0 means that no trigger programs at all
|
||||
** may be executed.
|
||||
*/
|
||||
#ifndef SQLITE_MAX_TRIGGER_DEPTH
|
||||
|
||||
Reference in New Issue
Block a user