Wednesday, August 14, 2019 6:19 AM
To: SQLite mailing list
Subject: Re: [sqlite] sqlite3_interrupt vs. SQLITE_CONFIG_SINGLETHREAD
On 8/14/19, Deon Brewis wrote:
> sqlite3_interrupt is documented as:
> “It is safe to call this routine from a thread different from the
> thread that is cur
On 8/14/19, Deon Brewis wrote:
> sqlite3_interrupt is documented as:
> “It is safe to call this routine from a thread different from the thread
> that is currently running the database operation”
>
> SQLITE_CONFIG_SINGLETHREAD is documented as:
> “puts SQLite into a mode where it can only be used
sqlite3_interrupt is documented as:
“It is safe to call this routine from a thread different from the thread that
is currently running the database operation”
SQLITE_CONFIG_SINGLETHREAD is documented as:
“puts SQLite into a mode where it can only be used by a single thread”
Which one wins 😉? i.e
3 matches
Mail list logo
