Lines Matching full:database
72 // Invoked on the database thread. The return value indicates whether the
152 // in-memory URL database. The returned pointer MAY BE NULL if the in-memory
153 // database has not been loaded yet. This pointer is owned by the history
187 // All "Add Page" functions will update the visited link database.
258 // in from the database. It is designed for rebuilding the visited link
259 // database from history.
275 // Queries the basic information about the URL in the history database. If
291 // history_types.h). If non-empty, the full-text database will be queried with
296 // database (see SetPageContents) which won't generally be set yet.
307 // If there is no such URL in the database or the most recent visit has no
383 // database or the request will be ignored.
393 // Database management operations --------------------------------------------
447 // the database with no need for a callback.
538 // callers to know when the history thread is complete and the database files
548 // into the database. This assumes the URL doesn't exist in the database
551 // dispatch to the history thread and will be a separate database
617 // database so it can query. See history_autocomplete.cc for a diagram.
679 // Sets the in-memory URL database. This is called by the backend once the
680 // database is loaded to make it available.
683 // Called by our BackendDelegate when there is a problem reading the database.
853 // autocomplete system. This will be NULL until the database has been created
