Lines Matching refs:corrupt
2654 ** deliberately corrupt the database file are disabled. The disabled
6591 ** open can result in a corrupt database.
6888 ** things may happen, including segmentation faults and corrupt database
11555 ** codes include SQLITE_CORRUPT (if the changeset buffer is corrupt) or
11958 ** appears to be corrupt and the corruption is detected, SQLITE_CORRUPT is
19547 ** that the database is definitely corrupt, only that it might be corrupt.
34865 /* We can only reach this point when reading a corrupt database
37654 ** could lead to a corrupt database.
40441 ** or power failure will likely corrupt the database file.
41411 ** system crash, the database itself may also become corrupt. */
42931 ** a '-' character. However in 8+3 filename mode, or if a corrupt
51607 /* This can only happen with a corrupt wal mode db */
53630 ** When reading a corrupt database file, it is possible that SQLite might
53640 ** corrupt, code at the b-tree layer may overread the page buffer and
55776 ** they upgrade to writers, they may inadvertently corrupt the database
57697 ** correct and the middle be corrupt. Thus, this "checksum" scheme,
57890 ** 2008-04-14: When attempting to vacuum a corrupt database file, it
59482 ** database image would become corrupt. It is therefore fortunate that
59703 ** while this is happening, the database could become corrupt.
65647 ** leave a corrupt WAL file on disk. */
65744 ** If the wal-header appears to be corrupt, try to reconstruct the
65791 ** works, but may fail if the wal-index header is corrupt or currently
66183 ** it finished. Leaving a corrupt image in the database file.
68056 ** this will be declared corrupt. This value is calculated based on a
68061 ** assumed that the database is corrupt.
69295 ** that the current key is corrupt. In that case, it is possible that
70519 ** indicates a corrupt database files:
70755 /* To many cells for a single page. The page must be corrupt */
73110 /* pBt->nPage might be zero if the database was corrupt when
73180 ** this lock. The iTable<1 term disables the check for corrupt schemas. */
73432 ** corrupt datrabase.
73856 ** of local content. Database must be corrupt. */
73921 ** in a corrupt database */
74561 ** If the record is corrupt, the xRecordCompare routine may read
75283 ** usableSize/4 - 8 entries will be reported as corrupt. In order
75377 ** file the database must be corrupt. */
75391 ** must not really be an overflow page and the database must be corrupt.
75751 /* In a corrupt database where an entry in the cell index section of
76039 ** database. But they might for a corrupt database. Hence use memmove()
76898 /* Sanity check: For a non-corrupt database file one of the follwing
77249 ** debugging. This is usually disabled because a corrupt database may
77342 ** This can occur if a database is corrupt with two or more SQL tables
77535 /* In a corrupt database, it is possible for the source and destination
77537 ** corrupt but it does cause valgrind and ASAN warnings. So use
77662 /* This can only happen if the schema is corrupt such that there is more
83315 ** Assert if an Abort at this point in time might result in a corrupt
86630 /* In a corrupt record entry, the last pMem might have been set up using
87506 ** pCur might be pointing to text obtained from a corrupt database file.
93258 /* Make sure a corrupt database has not given us an oversize header.
93281 ** this overread is harmless. Similar overreads can occur for a corrupt
93332 /* The record is corrupt if any of the following are true:
97217 ** the sqlite_schema table is corrupt. */
112757 ** from less than 3 to 4, as that will corrupt any preexisting DESC
114413 /* This can happen if the sqlite_schema table is corrupt */
116413 ** a corrupt record. Adding the two 0x00 bytes prevents this from causing
118472 sqlite3ErrorMsg(pParse, "corrupt database");
120724 if( iTable<2 ) sqlite3ErrorMsg(pParse, "corrupt schema");
137163 ** that the database is corrupt.
137202 ** This would indicate a corrupt schema.
137267 ** any other kind of statement while parsing the schema, even a corrupt
144673 ** clause in this obscure case, as doing so may corrupt the outer Select
147930 ** performance degradation, but false-negatives can result in a corrupt
147960 ** performance degradation, but false-negatives can result in a corrupt
149488 "corrupt database", P4_STATIC);
149554 ** corrupt the sqlite_schema.sql field with other kinds of statements
177727 ** formed and never corrupt. This flag is clear by default, indicating that
179410 ** guranteed that the database is not corrupt.
179965 ** structures should not be corrupt. Otherwise, true. If it is false, extra
179967 ** only true if it is guaranteed that the fts3 database is not corrupt.
180158 ** interested in. So, unless the doclist is corrupt, the 0x80 bit is
181499 ** The data structures are corrupt. */
191313 ** of these statements is untrue, then the data structure is corrupt.
194859 ** merge-hint is corrupt*/
197340 ** operation may fail if the database contains corrupt records.
201711 ** is greater than RTREE_MAX_DEPTH, the r-tree structure must be corrupt.
205095 "Dimension %d of cell %d on node %lld is corrupt", i, iCell, iNode
205107 "Dimension %d of cell %d on node %lld is corrupt relative to parent"
205253 rtreeCheckAppendMsg(&check, "Schema corrupt or not an rtree");
209509 sqlite3_result_error(context, "corrupt fossil delta", -1);
209520 sqlite3_result_error(context, "corrupt fossil delta", -1);
214215 ** buffer. This way small buffer overreads caused by corrupt database pages
218612 ** columns to be corrupt. This is convenient because otherwise,
218789 ** corrupt changeset. */
218854 ** Such records are technically corrupt, but the rebaser was at one
219683 ** corrupt changeset blob. */
222027 ** guranteed that the database is not corrupt.
225187 /* This is a corrupt record. So stop parsing it here. */
230255 ** without overreading if the records are corrupt.
235100 ** Or, if the input position-lists are corrupt, then the output might
235138 ** corrupt input position lists might cause the output to consume
236565 ** buffer overreads even if the record is corrupt. */
236659 sqlite3Fts5BufferSet(&rc, &s, 7, (const u8*)"corrupt");
236849 ** structures should not be corrupt. Otherwise, true. If it is false, extra
236851 ** only true if it is guaranteed that the fts5 database is not corrupt.
240863 /* nTotalRow being zero does not necessarily indicate a corrupt