On Fri, Mar 6, 2009 at 9:26 PM, Dan wrote:
> Why do you want to use a single sqlite3_stmt* from multiple threads
> at the same time?
Really the only thing I need to access is sqlite3_sql to copy the statement
to another thread.
We have an asynchronous API that we expose
On Mar 7, 2009, at 1:31 AM, Shawn Wilsher wrote:
> Hey all,
>
> I've been looking online for a bit trying to establish what
> protections, if
> any, are associated with sqlite3_stmt objects. It's clearly
> documented that
> sqlite3 objects' access is serialized across threads, but I cannot
Hey all,
I've been looking online for a bit trying to establish what protections, if
any, are associated with sqlite3_stmt objects. It's clearly documented that
sqlite3 objects' access is serialized across threads, but I cannot find
anything about sqlite3_stmt. I don't actually care either way,
3 matches
Mail list logo