--- ArtemGr <[EMAIL PROTECTED]> wrote:
> Joe Wilson wrote:
> > For the native sqlitejdbc driver, it should be straightforward to support
> > shared cache by calling sqlite3_enable_shared_cache(1) and recompiling
> > sqlitejdbc with a threadsafe version of sqlite 3.5. (As an added bonus, a
> > -DTHREADSAFE=1 compiled sqlite 3.5 would probably eliminate all the spurious
> > crashes seen in the native version of the sqlitejdbc driver related to
> > prepared statement finalization in different threads.)
>
> Well, -DTHREADSAFE=1 seems to be a good default for such always-
> threaded thing as JVM.
The native version of sqlitejdbc probably already uses -DTHREADSAFE=1,
which is the default compile setting for sqlite.
The new thing is that sqlite 3.5 is now fully threadsafe across all its
API calls for the first time. Before 3.5 it had a wierd and largely
undocumented mis-mash of inconsistant rules as to what you could safely
do with a connection between threads.
____________________________________________________________________________________
Got a little couch potato?
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---
