Hi all, sorry about my lack of responses in the last few weeks, especially neuro159, who offered up some very complete analyses. Besides being very busy, I'm working on some major internal changes, that will probably introduce a lot of bugs.
Before, all Statement objects were also ResultSet objects, so when you called something like executeQuery(), the statement simply returned itself. This led to a memory leak, as close() couldn't get rid of PreparedStatements, as it might have been the close() called on the ResultSet. Now a Statement encapsulates a single instance of a ResultSet, so the driver knows which close() was called, and can properly clean up the memory usage. I'd like to think this will make debugging easier too, but we'll see. In the next few days I'll post a binary snapshot. d. --~--~---------~--~----~------------~-------~--~----~ Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
