Lines Matching defs:SAVEPOINT_RELEASE
9987 #define SAVEPOINT_RELEASE 1
44633 ** Parameter op is always either SAVEPOINT_ROLLBACK or SAVEPOINT_RELEASE.
44634 ** If it is SAVEPOINT_RELEASE, then release and destroy the savepoint with
44651 ** are destroyed. If this is a release operation (op==SAVEPOINT_RELEASE),
44661 assert( op==SAVEPOINT_RELEASE || op==SAVEPOINT_ROLLBACK );
44672 nNew = iSavepoint + (( op==SAVEPOINT_RELEASE ) ? 0 : 1);
44680 if( op==SAVEPOINT_RELEASE ){
52754 ** or SAVEPOINT_RELEASE. This function either releases or rolls back the
52768 assert( op==SAVEPOINT_RELEASE || op==SAVEPOINT_ROLLBACK );
61518 ** SAVEPOINT_RELEASE. If it is SAVEPOINT_ROLLBACK, then the statement
61519 ** transaction is rolled back. If eOp is SAVEPOINT_RELEASE, then the
61538 assert( eOp==SAVEPOINT_ROLLBACK || eOp==SAVEPOINT_RELEASE);
61550 rc2 = sqlite3BtreeSavepoint(pBt, SAVEPOINT_RELEASE, iSavepoint);
61565 rc = sqlite3VtabSavepoint(db, SAVEPOINT_RELEASE, iSavepoint);
61732 eStatementOp = SAVEPOINT_RELEASE;
65994 rc = sqlite3VdbeCloseStatement(p, SAVEPOINT_RELEASE);
67506 assert( u.ar.p1==SAVEPOINT_BEGIN||u.ar.p1==SAVEPOINT_RELEASE||u.ar.p1==SAVEPOINT_ROLLBACK );
67568 }else if( db->writeVdbeCnt>0 && u.ar.p1==SAVEPOINT_RELEASE ){
67583 if( isTransaction && u.ar.p1==SAVEPOINT_RELEASE ){
67627 if( u.ar.p1==SAVEPOINT_RELEASE ){
84673 assert( !SAVEPOINT_BEGIN && SAVEPOINT_RELEASE==1 && SAVEPOINT_ROLLBACK==2 );
102340 ** SAVEPOINT_RELEASE, then the xRelease method of each virtual table with
102351 assert( op==SAVEPOINT_RELEASE||op==SAVEPOINT_ROLLBACK||op==SAVEPOINT_BEGIN );
109919 sqlite3Savepoint(pParse, SAVEPOINT_RELEASE, &yymsp[0].minor.yy0);
