Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Cecil Westerhof <Cecil@decebal.nl>
Newsgroups: comp.lang.python
Subject: Started to work with SQLite3 in Python3
Date: Sun, 20 Sep 2015 17:49:52 +0200
Organization: Decebal Computing
Lines: 21
Message-ID: <87fv29rsyn.fsf@Equus.decebal.nl>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="528adfd6ad074c92fdc6a7f8fb9e23d8"; logging-data="21637"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+hD7ICsMkqUJ/ZdfWbE4j2W/3Z6ZeqCDE="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
X-Homepage: http://www.decebal.nl/
Cancel-Lock: sha1:JNY6x7yqCUcRV4tSyCD/g1mk8eU= sha1:qM+RPuM/J+mW2SMwW46igaAr564=
Xref: csiph.com comp.lang.python:96883

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