Despite what the sqlite wiki says, I think sqlite3_finalize now works
from another thread as long as nothing else is using that sqlite3
connection or any prepared statements on that connection. Of course,
I could be wrong.
Search the sqlite mailing list archives in the past year
where they discuss this stuff in great detail.
--- jolz <[EMAIL PROTECTED]> wrote:
> Diriver calls sqlite functions in finalize body. That means that those
> functions are called from different thread that started the query
> which is illegal in sqlite.
> >From sqlite wiki:
> "So, beginning with version 3.3.1, the common paradigm of maintaining
> a pool of database connections and handing them off to worker threads
> for processing should work fine - as long as your worker threads are
> careful to finalize all of their prepared statements prior to
> exiting."
> Currently sqlite3_finalize may be (and sometime is) called different
> thread that is should.
____________________________________________________________________________________Take
the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news,
photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SQLiteJDBC" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlitejdbc?hl=en
-~----------~----~----~----~------~----~------~--~---
