In my code I'm opening a sqlite connection and keeping it open rather than opening and closing one on each transaction. Generally it's working well. I often save and close my image. When I then reopen the image I still have a connection and it says it's open, but using it gives me an error. This is easily recovered. I just open a new connection. Is there a way I can see if a connection is still good, in my code? Or should I be opening and closing connections every transaction? I haven't benchmarked it but I'm assuming it would be slower. I guess I could set my connection to nil in a start-up script. That would cause my code to get a new connection after a break from development. Any recommendations? Thanks, Jeff.
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
