Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #96883

Started to work with SQLite3 in Python3

From Cecil Westerhof <Cecil@decebal.nl>
Newsgroups comp.lang.python
Subject Started to work with SQLite3 in Python3
Date 2015-09-20 17:49 +0200
Organization Decebal Computing
Message-ID <87fv29rsyn.fsf@Equus.decebal.nl> (permalink)

Show all headers | View raw


I started a little project in Python3 with SQLite3:
    https://github.com/CecilWesterhof/CarApplication

I do not mind to get some feedback on it.

I was wondering about two things:
- Would it be better to split the code into several parts. (For
  example the SQL statements.)
- 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.

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

Back to comp.lang.python | Previous | NextNext in thread | Find similar | Unroll thread


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