Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Neil Cerutti Newsgroups: comp.lang.python Subject: Re: Best practice for connections and cursors Date: 1 Aug 2013 15:20:32 GMT Organization: Norwich University Lines: 15 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: individual.net xzZchNVdqSfaXU7yj/EbzQiR4M0teOuL0lxIap6yfpDmBwqCA6 Cancel-Lock: sha1:1Bvvo5ZGljbn9Y49AOcUk3U2CVg= User-Agent: slrn/0.9.9p1/mm/ao (Win32) Xref: csiph.com comp.lang.python:51738 On 2013-08-01, Joseph L. Casale wrote: > A bit vague I know, but does anyone see the obvious mistake? I > assumed the module setting up a singleton connection was a > perfectly viable way to accomplish this? My one db application started out creating a new connection to the db (sqlite3) for every select and insert. When I converted it to maintaining it's own single connection and creating new cursors instead it was a huge speed increase. So I too am interested in the answers you'll hopefully be getting. I have no plans for utilizing concurrent access to the db, but maybe I'll want to someday. -- Neil Cerutti