Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Cecil Westerhof Newsgroups: comp.lang.java.programmer Subject: Not closing a SQL(ite3) connection Date: Wed, 09 Aug 2017 11:28:29 +0200 Organization: Decebal Computing Lines: 12 Message-ID: <87a839um2q.fsf@munus.decebal.nl> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="75662a87a83d79e99d1b79ff65a19ab5"; logging-data="26645"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX186msXgDk6df4npkmO7FMqQ3/9uVAvpJGo=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-Homepage: http://www.decebal.nl/ Cancel-Lock: sha1:7USMLEDEFHsF9GC0f9ULtdpnWI8= sha1:4ayoHtHquscvaaC3RShsk4YH8IE= Xref: csiph.com comp.lang.java.programmer:37106 Normally I always close a connection when finished. But I now wrote my own class SQLite3 to handle things in this class. It has its own connection. Can there be a problem when a connection is not closed, or is that not something to worry myself about? Would it be a good idea to write a function to close the database connection? -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof