Searched refs:OP_Destroy (Results 1 - 6 of 6) sorted by relevance

/external/chromium_org/third_party/sqlite/src/src/
H A Dvdbeaux.c349 ** * OP_Destroy
370 if( opcode==OP_Destroy || opcode==OP_VUpdate || opcode==OP_VRename
H A Dbuild.c1907 sqlite3VdbeAddOp3(v, OP_Destroy, iTable, r1, iDb);
1910 /* OP_Destroy stores an in integer r1. If this integer
1942 ** is not defined), then it is important to call OP_Destroy on the
1945 ** to be destroyed is relocated by an earlier OP_Destroy. i.e. if the
1948 ** OP_Destroy 4 0
1950 ** OP_Destroy 5 0
1954 ** "OP_Destroy 4 0" opcode. The subsequent "OP_Destroy 5 0" would hit
H A Dvdbe.c4506 case OP_Destroy: { /* out2-prerelease */
4535 /* All OP_Destroy operations occur on the same btree */
/external/chromium_org/third_party/sqlite/amalgamation/
H A Dsqlite3.c8135 #define OP_Destroy 95 macro
[all...]
/external/sqlite/dist/orig/
H A Dsqlite3.c9369 #define OP_Destroy 115 macro
[all...]
/external/sqlite/dist/
H A Dsqlite3.c9369 #define OP_Destroy 115 macro
[all...]

Completed in 427 milliseconds