--- ArtemGr <[EMAIL PROTECTED]> wrote:
> > If you do I will add it to the test suite so there are no regessions.
> >
> > d.
>
> Here it is.
> http://pastebin.com/942825
> Currently it either SIGSEGVs or hangs under native, throws an
> Exception under nested.
That's a good test case.
This test on SQLiteJDBC under NestedVM produces:
java.sql.SQLException: not an error
at org.sqlite.DB.execute(DB.java:226)
at org.sqlite.DB.executeUpdate(DB.java:242)
at org.sqlite.Stmt.executeUpdate(Stmt.java:83)
at Main$2.run(Main.java:40)
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.
But you're also sharing one Statement instance across all threads.
That might be a factor as well (even though executeUpdate is
synchronized).
Should be interesting to solve.
____________________________________________________________________________________
Shape Yahoo! in your own image. Join our Network Research Panel today!
http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---
