Hi David! When using the close()-method of your org.sqlite.Conn-class, it just calls the db.close() method, but it does not set the db-field to null. So, any subsequent call of isClosed() will return true even if the connection has already been closed!
Would you _please_ release an updated version solving this problem? Best thing would be if you could also try to fix this temp-file problem Jow Wilson described right here: http://groups.google.com/ group/sqlitejdbc/browse_thread/thread/ 220d2b30b21cbb13/40272ced421f044e Like it's now I have to delete them manually on my Windows-machine... Love your work, Stefan BTW: If you need someone who helps you with the development or something like that ask me ;-) Really a nice lib... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLiteJDBC" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlitejdbc?hl=en -~----------~----~----~----~------~----~------~--~---
