Lines Matching full:safe
684 ** the mutexes are omitted. Without the mutexes, it is not safe
1213 ** in a thread-safe way. The [sqlite3_vfs_find()] interface
1612 ** are enabled so that SQLite will be safe to use in a multi-threaded
1966 ** ^It is safe to call this routine from a thread different from the
1968 ** is not safe to call this routine with a [database connection] that
2138 ** It is not safe to pass a result table directly to [sqlite3_free()].
4239 ** It is not safe to read or modify this variable in more than one
4240 ** thread at a time. It is not safe to read or modify this variable
4958 ** way that makes it safe to invoke [sqlite3_blob_close()] on *ppBlob
8700 ** explanation as to why it is safe to add an entry to an sqlite3.pDisconnect
21422 ** If we are to be thread-safe, include the pthreads header and define
24430 ** Others do no. To be safe, we will stick with the (slower) fsync().
25080 ** findLockInfo(). If this is the case, it is quite safe to close
25084 ** If scenario (a) caused the error then things are not so safe. The
25492 /* It is safe to close fd at this point, because it is guaranteed not
25494 ** it would not be safe to close as this would release any locks held
25877 ** database file to coordinate safe, concurrent access by multiple readers
25964 ** normally taken on the database file. This allows for safe sharing
31751 ** a non-testing build. These variables are not thread-safe.
32999 ** unsynced portion of the main journal file, then it is not safe
33187 /* TODO: Is it safe to use Pager.dbFileSize here? */
35026 ** database is safe to read while this process is still rolling the
36037 ** property of the host file-system, this is safe.
36213 ** So is safe to finalize the journal file even if the playback
36223 ** playback operation did not succeed it would not be safe to finalize
38316 ** free-list for reuse. It returns false if it is safe to retrieve the
43549 ** This is safe because dropping a cell only overwrites the first
43551 ** four bytes of the divider cell. So the pointer is safe to use
44192 ** has completed, it is safe to release the pSpace buffer used by
45504 ** open so it is safe to access without the BtShared mutex.
45517 ** open so it is safe to access without the BtShared mutex.
45734 ** structure may be accessed via two groups of thread-safe entry points:
45748 ** backup_pagecount() are not thread-safe functions. If they are called
46427 ** malloc(). In this way, we know that the memory is safe to be
48141 /* Note: this cast is safe, because the origin data point was an int
63925 ** identical, we return FALSE just to be safe. So if this routine
67761 ** 1 chance in 2^32. So we're safe enough.
68809 ** since sqlite3ReleaseTempRange() was called, it is safe to do so.
69992 ** to take the safe route and skip the optimization.
85782 ** was committed at the btree level). So it safe to end the transaction
85948 ** this makes it safe to access the sqlite3.pDisconnect list of any
85992 ** by multiple threads. It is thread-safe.
95662 ** routine is not threadsafe. But it is safe to invoke this routine
99712 ** Value used to signify the end of an offset-list. This is safe because
100391 ** so that it is safe to use pList as the output as well as an input
106203 /* It is not safe to call isspace(), tolower(), or isalnum() on
