Lines Matching full:statement
23 class Statement;
25 // Uniquely identifies a statement. There are two modes of operation:
28 // identify your statement. This is a convienient way to get uniqueness for
29 // a statement that is only used in one place. Use the SQL_FROM_HERE macro
32 // - In the "custom" mode you may use the statement from different places or
42 // Creates a uniquely named statement with the given file ane line number.
49 // Creates a uniquely named statement with the given user-defined name.
57 // a statement name that will be deallocated and will cause a crash later.
75 // false while the actual error code and causing statement are delivered using
85 // our best guess at the statement that triggered the error. Do not store
88 // |stmt| MAY BE NULL if there is no statement causing the problem (i.e. on
91 // If the error condition has been fixed an the original statement succesfuly
94 virtual int OnError(int error, Connection* connection, Statement* stmt) = 0;
208 // Returns true if we have a statement with the given identifier already
214 // Returns a statement for the given SQL using the statement cache. It can
215 // take a nontrivial amount of work to parse and compile a statement, so
220 // statement before using it.
226 // You will normally use the SQL_FROM_HERE macro to generate a statement
231 // sql::Statement stmt(connection_.GetCachedStatement(
234 // return false; // Error creating statement.
238 // Returns a non-cached statement for the given SQL. Use this for SQL that
240 // keeping a statement cached).
258 // statement executed. Will be 0 if no statement has executed or the database
276 // Statement access StatementRef which we don't want to expose to erverybody
277 // (they should go through Statement).
278 friend class Statement;
285 // A StatementRef is a refcounted wrapper around a sqlite statement pointer.
286 // Refcounting allows us to give these statements out to sql::Statement
290 // A statement ref can be valid, in which case it can be used, or invalid to
291 // indicate that the statement hasn't been created yet, has an error, or has
298 // Default constructor initializes to an invalid statement.
302 // When true, the statement can be used.
309 // Returns the sqlite statement if any. If the statement is not active,
313 // Destroys the compiled statement and marks it NULL. The statement will
329 // Executes a rollback statement, ignoring all transaction state. Used
341 // Called by Statement objects when an sqlite function returns an error.
343 int OnSqliteError(int err, Statement* stmt);
