Searched refs:nested (Results 1 – 25 of 37) sorted by relevance
12
104 return sqlite3WritableSchema(db)==0 && pParse->nested==0; in tabIsReadOnly()410 if( pParse->nested==0 ) sqlite3VdbeCountChanges(v); in sqlite3DeleteFrom()440 && !pParse->nested in sqlite3DeleteFrom()637 int count = (pParse->nested==0); /* True to count changes */ in sqlite3DeleteFrom()659 if( pParse->nested==0 && pParse->pTriggerTab==0 ){ in sqlite3DeleteFrom()837 if( pParse->nested==0 || 0==sqlite3_stricmp(pTab->zName, "sqlite_stat1") ){ in sqlite3GenerateRowDelete()
602 if( pParse->nested==0 ) sqlite3VdbeCountChanges(v); in sqlite3Update()667 && !pParse->nested in sqlite3Update()734 if( !pParse->nested && !pTrigger && !hasFK && !chngKey && !bReplace ){ in sqlite3Update()1073 if( !pParse->nested ){ in sqlite3Update()1128 if( pParse->nested==0 && pParse->pTriggerTab==0 && pUpsert==0 ){ in sqlite3Update()
805 if( pParse->nested==0 ) sqlite3VdbeCountChanges(v); in sqlite3Insert()1038 && !pParse->nested in sqlite3Insert()1413 if( pParse->nested==0 && pParse->pTriggerTab==0 ){ in sqlite3Insert()2600 if( pParse->nested ){ in sqlite3CompleteInsertion()2613 if( !pParse->nested ){ in sqlite3CompleteInsertion()
148 if( pParse->nested ) return; in sqlite3FinishCoding()310 assert( pParse->nested<10 ); /* Nesting should only be of limited depth */ in sqlite3NestedParse()322 pParse->nested++; in sqlite3NestedParse()330 pParse->nested--; in sqlite3NestedParse()1065 if( (pParse->nested==0 && 0==sqlite3StrNICmp(zName, "sqlite_", 7)) in sqlite3CheckObjectName()2933 assert( !pParse->nested ); in sqlite3EndTable()5325 assert( (errCode&0xff)==SQLITE_CONSTRAINT || pParse->nested ); in sqlite3HaltConstraint()
575 assert( pParse->nested==0 ); in sqlite3ParseObjectReset()
119 # The following tests, tkt3718-2.*, test that a nested statement 154 # that has a committed statement transaction nested inside of it can
14 # it tests the special handling of nested SQL statements (those executed
100 # nested in savepoint "one".
145 # Check that RAISE(IGNORE) works correctly for nested triggers:
108 # Query planner fault on three-way nested join with compound inner SELECT
10 # focus of this file is testing compute SELECT statements and nested
697 # Stack overflow on deeply nested JSON.699 # The following tests confirm that deeply nested JSON is considered invalid.
208 # 5.x - complex tests with temporary tables and nested instead of triggers
232 # Make sure the max(x) and min(x) optimizations work for nested
294 # 7.x - complex tests with temporary tables and nested instead of triggers
194 # two nested aggregate queries.
1520 # Verify that a nested savepoint may be released without satisfying 1523 # EVIDENCE-OF: R-07223-48323 A nested savepoint transaction may be1562 # EVIDENCE-OF: R-44295-13823 A transaction savepoint (a non-nested1602 # constraints, any nested savepoints remain open.1607 # currently nested savepoints, the nested savepoints remain open.
171 # Incorrect result in a nested GROUP BY/DISTINCT due to the use of an OP_SCopy
243 # Make sure the max(x) and min(x) optimizations work for nested
478 # LIMIT does not work with nested views containing UNION ALL
386 # Check that the flattener works correctly for deeply nested subqueries
475 # nested query. This test caused a segfault on 3.8.5 beta.
111 # Test OOM injection with nested colsets.
508 REM NOTE: Launch a nested command shell to perform the following steps:746 REM NOTE: Handle any errors generated during the nested command shell.
331 also present in any nested packages.