Lines Matching full:transaction
134 // transaction, which means there may be less time spent initializing the
135 // next transaction because it doesn't have to re-aquire locks.
175 // database, as it openes a transaction on the meta table to force the
184 // Transaction management. We maintain a virtual transaction stack to emulate
186 // limitation is you can't roll back a sub transaction: if any transaction
191 // Normally you should use sql::Transaction to manage a transaction, which
197 // Returns the current transaction nesting, which will be 0 if there are
329 // Executes a rollback statement, ignoring all transaction state. Used
330 // internally in the transaction management code.
374 // When we get to the outermost transaction, this will determine if we do
