Joe Wilson <[EMAIL PROTECTED]> wrote: > Looking at DB.java ... > > case SQLITE_MISUSE: > throw new SQLException(errmsg()); > > It is probably related to Nested SQLiteJDBC not being compiled > with thread support due to NestedVM not supporting threads.
Ah, but I get the same error on the native build. I thought it might be my fix for the custom function code, but if you remove the custom function from the test case, you get the same error. Any number of MISUSEs can be thrown, from zero to dozens, and it's always from executeUpdate(). So it's definitely a race condition. This is very strange, as executeUpdate() is, as you say, synchronized. I'll take another look later today. d. --~--~---------~--~----~------------~-------~--~----~ Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
