On Mar 9, 11:37 pm, "David Crawshaw" <[EMAIL PROTECTED]> wrote: <snip> > So now I can start to see how you are locking for 2-5 seconds. It > wouldn't take too much of a hardware downgrade to see those numbers. > As always, I recommend using the native driver. As my last bungle > demonstrates, you can distribute the nested jar file with the library > files for each platform, telling people to put them on the library > path. E.g package: > > sqlitejdbc-v042-nested.jar > libsqlitejdbc.jnilib > sqlitejdbc.dll > libsqlitejdbc.so > > And make sure your program is started with > -Djava.library.path=whereever. This way it will use the native if > possible, otherwise it will fall back on the nested. > > I really should put up instructions for this on the website. There > will also probably be a new version in a few days that lets you set > the timeout and uses a special subclass of SQLException for "db is > locked". > > d.
Didn't see this reply before I posted my last one. This is a very interesting fact! I didn't realize the nested jar would pickup and use the native lib if it was available (definitely web site worthy material ;-). I've been staying away from the native driver because I didn't want to have to package multiple versions of my app, but if the nested jar will look for and use the native lib then I can definitely take advantage of that and probably avoid this whole issue. - Derek --~--~---------~--~----~------------~-------~--~----~ Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
