Lines Matching defs:hit
21912 ** a performance hit but it is not a fatal error. So mark the
25212 ** should never be hit, as this function should only be called after
38943 ** take the performance hit.
41438 ** all data has really hit the disk before nRec is updated to mark
44576 ** the search is guaranteed to eventually hit an unused entry. Let
55890 char *hit = 0;
56028 hit = sqlite3PageMalloc( pBt->pageSize );
56029 if( hit==0 ){
56034 memset(hit+contentOffset, 0, usableSize-contentOffset);
56035 memset(hit, 1, contentOffset);
56049 for(j=pc+size-1; j>=pc; j--) hit[j]++;
56058 for(j=i+size-1; j>=i; j--) hit[j]++;
56065 if( hit[i]==0 ){
56067 }else if( hit[i]>1 ){
56079 sqlite3PageFree(hit);
56630 ** error was hit. The error has already been written into the
59389 ** callgrind, this causes a certain test case to hit the CPU 4.7
60507 ** or hit an 'OR FAIL' constraint and there are no deferred foreign
74263 ** be a small performance hit but is otherwise harmless. On the other
81088 ** "OP_Destroy 4 0" opcode. The subsequent "OP_Destroy 5 0" would hit
94279 int iBreak /* Jump here if we hit the LIMIT */
103129 int nSingle = 0; /* Histogram regions hit by a single value */
103133 u8 aSingle[SQLITE_INDEX_SAMPLES+1]; /* Histogram regions hit once */
104747 VdbeComment((v, "record LEFT JOIN hit"));
116828 ** subsequently to determine whether or not an EOF was hit.
125447 ** the %_content table. If we hit the duplicate rowid constraint (or any