Lines Matching defs:SAVEPOINT_RELEASE
9987 #define SAVEPOINT_RELEASE 1
44661 ** Parameter op is always either SAVEPOINT_ROLLBACK or SAVEPOINT_RELEASE.
44662 ** If it is SAVEPOINT_RELEASE, then release and destroy the savepoint with
44679 ** are destroyed. If this is a release operation (op==SAVEPOINT_RELEASE),
44689 assert( op==SAVEPOINT_RELEASE || op==SAVEPOINT_ROLLBACK );
44700 nNew = iSavepoint + (( op==SAVEPOINT_RELEASE ) ? 0 : 1);
44708 if( op==SAVEPOINT_RELEASE ){
52782 ** or SAVEPOINT_RELEASE. This function either releases or rolls back the
52796 assert( op==SAVEPOINT_RELEASE || op==SAVEPOINT_ROLLBACK );
61546 ** SAVEPOINT_RELEASE. If it is SAVEPOINT_ROLLBACK, then the statement
61547 ** transaction is rolled back. If eOp is SAVEPOINT_RELEASE, then the
61566 assert( eOp==SAVEPOINT_ROLLBACK || eOp==SAVEPOINT_RELEASE);
61578 rc2 = sqlite3BtreeSavepoint(pBt, SAVEPOINT_RELEASE, iSavepoint);
61593 rc = sqlite3VtabSavepoint(db, SAVEPOINT_RELEASE, iSavepoint);
61760 eStatementOp = SAVEPOINT_RELEASE;
66022 rc = sqlite3VdbeCloseStatement(p, SAVEPOINT_RELEASE);
67534 assert( u.ar.p1==SAVEPOINT_BEGIN||u.ar.p1==SAVEPOINT_RELEASE||u.ar.p1==SAVEPOINT_ROLLBACK );
67596 }else if( db->writeVdbeCnt>0 && u.ar.p1==SAVEPOINT_RELEASE ){
67611 if( isTransaction && u.ar.p1==SAVEPOINT_RELEASE ){
67655 if( u.ar.p1==SAVEPOINT_RELEASE ){
84709 assert( !SAVEPOINT_BEGIN && SAVEPOINT_RELEASE==1 && SAVEPOINT_ROLLBACK==2 );
102376 ** SAVEPOINT_RELEASE, then the xRelease method of each virtual table with
102387 assert( op==SAVEPOINT_RELEASE||op==SAVEPOINT_ROLLBACK||op==SAVEPOINT_BEGIN );
109955 sqlite3Savepoint(pParse, SAVEPOINT_RELEASE, &yymsp[0].minor.yy0);
