Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #51738
| From | Neil Cerutti <neilc@norwich.edu> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Best practice for connections and cursors |
| Date | 2013-08-01 15:20 +0000 |
| Organization | Norwich University |
| Message-ID | <b5vcm0F8577U1@mid.individual.net> (permalink) |
| References | <mailman.80.1375369534.1251.python-list@python.org> |
On 2013-08-01, Joseph L. Casale <jcasale@activenetwerx.com> 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
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Best practice for connections and cursors "Joseph L. Casale" <jcasale@activenetwerx.com> - 2013-08-01 15:05 +0000 Re: Best practice for connections and cursors Neil Cerutti <neilc@norwich.edu> - 2013-08-01 15:20 +0000
csiph-web