Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #96886
| References | <87fv29rsyn.fsf@Equus.decebal.nl> |
|---|---|
| Date | 2015-09-21 02:44 +1000 |
| Subject | Re: Started to work with SQLite3 in Python3 |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.43.1442767480.21674.python-list@python.org> (permalink) |
On Mon, Sep 21, 2015 at 1:49 AM, Cecil Westerhof <Cecil@decebal.nl> wrote: > - I understood that with > for fuel in fuel_cursor: > a fetchall will be executed. > At the moment I do not see this as a problem, but if the table would > become very big it could. Would it be better to rewrite it with a > fetchone? > But that is then needed inside and before the loop. What would be a > little ugly. It iterates over the query, but it doesn't fetchall() into a list. So it's as good as using fetchone(). ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Started to work with SQLite3 in Python3 Cecil Westerhof <Cecil@decebal.nl> - 2015-09-20 17:49 +0200
Re: Started to work with SQLite3 in Python3 Chris Angelico <rosuav@gmail.com> - 2015-09-21 02:44 +1000
Re: Started to work with SQLite3 in Python3 Cecil Westerhof <Cecil@decebal.nl> - 2015-09-20 20:40 +0200
Re: Started to work with SQLite3 in Python3 Cecil Westerhof <Cecil@decebal.nl> - 2015-09-20 20:57 +0200
Re: Started to work with SQLite3 in Python3 Cecil Westerhof <Cecil@decebal.nl> - 2015-09-20 21:03 +0200
csiph-web