Lines Matching refs:likely
3073 ** of a table column that its values are likely to be very large - larger
4712 ** undefined and is likely a memory access violation.
6691 ** SQLITE_TRANSIENT value means that the content will likely change in
7969 ** to read or write the estimatedRows field are undefined (but are likely
9153 ** [SQLITE_DBSTATUS options] is likely
13934 ** expression that is usually false. Macro likely() surrounds
13939 #define likely(X) (X)
15383 #define BTREE_APPEND 0x08 /* Insert is likely an append */
16477 ** anybody smart enough to figure out the code is also likely smart
16544 ** windows and unix. I'm guessing that isn't likely to happen, but by
17159 #define SQLITE_Defensive 0x10000000 /* Input SQL is likely hostile */
17318 #define SQLITE_FUNC_SUBTYPE 0x00100000 /* Result likely to have sub-type */
19055 #define OPFLAG_APPEND 0x08 /* This is likely to be an append */
24472 ** much more likely to break and we are much more liking to find
37448 ** or power failure will likely corrupt the database file.
38390 ** same database file at the same time, database corruption will likely
52893 ** because garbage data that appears at the end of a journal is likely
54331 ** If journal corruption occurs due to a power failure, the most likely
54333 ** It is much less likely that the two ends of the journal record will be
54335 ** though fast and simple, catches the mostly likely kind of corruption.
56235 ** with this page cache after this function returns will likely
58666 ** not the case. In this case it is likely enough that the redundant
67277 ** call to btreeInitPage() will likely return SQLITE_CORRUPT.
73639 int flags, /* True if this is likely an append */
91768 ** that this insert is likely to be an append.
95034 ** to sqlite3ThreadJoin() is likely to block. Cases that are likely to
99557 ** EVIDENCE-OF: R-36850-34127 The likely(X) function is short-hand
99559 ** EVIDENCE-OF: R-53436-40973 The likely(X) function is equivalent
99561 /* TUNING: unlikely() probability is 0.0625. likely() is 0.9375 */
100791 ** or likelihood() or likely() functions at the root of an
102963 ** will likely result in an incorrect answer. So when in doubt, return
120573 INLINE_FUNC(likely, 1, INLINEFUNC_unlikely, SQLITE_FUNC_UNLIKELY),
122816 u8 appendFlag = 0; /* True if the insert is likely to be an append */
124626 int appendBias, /* True if this is likely to be an append */
129617 ** The rules for when tables are analyzed are likely to change in
130682 ** more likely to cause a segfault than -1 (of course there are assert()
150591 ** likely(), or unlikely() SQL functions, reduce the estimated number
151009 /* TUNING: Mark terms as "low selectivity" if they seem likely
151118 ** add a 1.375 fudge factor to make skip-scan slightly less likely. */
168481 ** an error that we cannot easily detect but that will likely cause memory
169219 ** likely to be query targets.
169340 ** argument for MERGE_COUNT of 16. Also, it is possible/likely that
198445 ** committed before the RBU update database this will likely either just
198499 ** Additionally, because the index updates are likely to be applied in
198500 ** random order, access to pages within the database is also likely to be in
224326 /* fts5WriteInit() should have initialized the buffers to (most likely)