Lines Matching refs:SQLITE_FULL
891 #define SQLITE_FULL 13 /* Insertion failed because database is full */
4271 ** transaction (errors including [SQLITE_FULL], [SQLITE_IOERR],
20282 SimulateDiskfullError( return SQLITE_FULL );
20296 return ( rc != NO_ERROR || amt > (int)wrote ) ? SQLITE_FULL : SQLITE_OK;
24388 return SQLITE_FULL;
24539 /* Unix cannot, but some systems may return SQLITE_FULL from here. This
24542 SimulateDiskfullError( return SQLITE_FULL );
27789 return SQLITE_FULL;
27823 SimulateDiskfullError(return SQLITE_FULL);
27828 return SQLITE_FULL;
27841 return SQLITE_FULL;
31371 ** or SQLITE_FULL. Once one of the first three errors occurs, it persists
31373 ** SQLITE_FULL return code is slightly different. It persists only until the
31375 ** SQLITE_FULL does not affect the sqlite3PagerGet() and sqlite3PagerLookup()
32382 ** If the second argument is SQLITE_IOERR, SQLITE_CORRUPT, or SQLITE_FULL
32398 pPager->errCode==SQLITE_FULL ||
32402 if( rc2==SQLITE_FULL || rc2==SQLITE_IOERR ){
33530 ** one of SQLITE_IOERR, SQLITE_CORRUPT or SQLITE_FULL).
34752 ** pager is in an error state other than SQLITE_FULL when this is called,
34754 ** database when in SQLITE_FULL error state.
35022 if( pPager->errCode!=SQLITE_OK && pPager->errCode!=SQLITE_FULL ){
35068 rc = SQLITE_FULL;
35119 ** or if the pager is in an error state other than SQLITE_FULL.
35989 ** * If in an error state other than SQLITE_FULL, then task (1) is
36020 }else if( pPager->errCode && pPager->errCode!=SQLITE_FULL ){
39163 ** SQLITE_CORRUPT or some other error (i.e. SQLITE_FULL). Check that this
49167 ** SQLITE_FULL
49197 || mrc==SQLITE_INTERRUPT || mrc==SQLITE_FULL;
49203 if( (mrc==SQLITE_NOMEM || mrc==SQLITE_FULL) && p->usesStmtJournal ){
55785 ** a SQLITE_FULL error is generated. The P3 register is updated with the '
55873 rc = SQLITE_FULL; /* IMP: R-12275-61338 */
55906 rc = SQLITE_FULL; /* IMP: R-38219-53002 */
95969 /* SQLITE_FULL */ "database or disk is full",
107719 ** If there is not enough free space in pNode, return SQLITE_FULL.