Hi All, I just upgraded to version 0.51 (from 0.40) and discovered the statement closing exception. Can anybody suggest a workaround or point me to a jar with a fix? I am currently just ignoring it, but I'm afraid this will lead to its own problems.
Thanks, Dan Riegel On Jun 24, 7:05 am, "David Crawshaw" <[EMAIL PROTECTED]> wrote: > 2008/6/24 Dan Karp <[EMAIL PROTECTED]>: > > > Any chance that closing an already-closed statement could be changed > > to a no-op? Closing an already-closed ResultSet doesn't throw an > > exception... > > It's a bug, introduced in my big reorganisation. It will be fixed in > the next release. > > d. --~--~---------~--~----~------------~-------~--~----~ Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
