Lines Matching defs:likely
2414 ** of a table column that its values are likely to be very large - larger
4085 ** undefined and is likely a memory access violation.
6114 ** SQLITE_TRANSIENT value means that the content will likely change in
7524 ** to read or write the estimatedRows field are undefined (but are likely
8742 ** [SQLITE_DBSTATUS options] is likely
13878 ** expression that is usually false. Macro likely() surrounds
13883 #define likely(X) (X)
15010 ** anybody smart enough to figure out the code is also likely smart
15077 ** windows and unix. I'm guessing that isn't likely to happen, but by
15690 #define BTREE_APPEND 0x08 /* Insert is likely an append */
17209 #define SQLITE_Defensive 0x10000000 /* Input SQL is likely hostile */
17378 #define SQLITE_FUNC_SUBTYPE 0x00100000 /* Result likely to have sub-type */
19279 #define OPFLAG_APPEND 0x08 /* This is likely to be an append */
26099 ** much more likely to break and we are much more liking to find
40441 ** or power failure will likely corrupt the database file.
41465 ** same database file at the same time, database corruption will likely
56249 ** because garbage data that appears at the end of a journal is likely
57694 ** If journal corruption occurs due to a power failure, the most likely
57696 ** It is much less likely that the two ends of the journal record will be
57698 ** though fast and simple, catches the mostly likely kind of corruption.
59666 ** with this page cache after this function returns will likely
62116 ** not the case. In this case it is likely enough that the redundant
71026 ** call to btreeInitPage() will likely return SQLITE_CORRUPT.
77631 int flags, /* True if this is likely an append */
96651 ** that this insert is likely to be an append.
100063 ** to sqlite3ThreadJoin() is likely to block. Cases that are likely to
104703 ** EVIDENCE-OF: R-36850-34127 The likely(X) function is short-hand
104705 ** EVIDENCE-OF: R-53436-40973 The likely(X) function is equivalent
104707 /* TUNING: unlikely() probability is 0.0625. likely() is 0.9375 */
105950 ** or likelihood() or likely() functions at the root of an
108304 ** will likely result in an incorrect answer. So when in doubt, return
126980 INLINE_FUNC(likely, 1, INLINEFUNC_unlikely, SQLITE_FUNC_UNLIKELY),
129310 u8 appendFlag = 0; /* True if the insert is likely to be an append */
131162 int appendBias, /* True if this is likely to be an append */
136577 ** The rules for when tables are analyzed are likely to change in
137694 ** more likely to cause a segfault than -1 (of course there are assert()
159149 ** likely(), or unlikely() SQL functions, reduce the estimated number
159602 /* TUNING: Mark terms as "low selectivity" if they seem likely
159713 ** add a 1.375 fudge factor to make skip-scan slightly less likely. */
178096 ** an error that we cannot easily detect but that will likely cause memory
178854 ** likely to be query targets.
178975 ** argument for MERGE_COUNT of 16. Also, it is possible/likely that
208237 ** committed before the RBU update database this will likely either just
208291 ** Additionally, because the index updates are likely to be applied in
208292 ** random order, access to pages within the database is also likely to be in
234603 /* fts5WriteInit() should have initialized the buffers to (most likely)