How to use SQLite (sqlite3) more efficiently

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path	<ps16thypresenceisfullnessofjoy@gmail.com>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.015
X-Spam-Evidence	'H': 0.97; 'S': 0.00; 'scripts': 0.03; 'insert': 0.05; 'preference': 0.07; 'alias': 0.09; 'back.': 0.09; 'subject:How': 0.10; 'sqlite': 0.16; 'subject:sqlite3': 0.16; 'pointed': 0.19; 'seems': 0.21; 'header:User-Agent:1': 0.23; 'logical': 0.24; 'replace': 0.24; 'mention': 0.26; 'subject:) ': 0.29; 'forgot': 0.30; 'code': 0.31; 'update.': 0.31; '(including': 0.33; 'says': 0.33; 'subject: (': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'message- id:@gmail.com': 0.38; 'to:addr:python-list': 0.38; 'to:addr:python.org': 0.39; 'changed': 0.39; 'new': 0.61; 'subject:more': 0.64; 'more': 0.64; 'timothy': 0.84; 'engines.': 0.91; 'engines,': 0.93
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=cezIu4vclgdXwu3a+VhrCSytA6j8RBalkgmVELA7MO0=; b=D4fBZ1KDLiTTFYHZFxp8vt7VL0loh4QDlHWj8D0RnpDPWJ0oKoP19ctxbqL3BoKwJ3 pcJSBle95RlMjLJCmL0jP1pvY/fMyvLZs7FFGw0h0viv13YhKUr0Cj2eWW8SVoa+9HbG MwLcyHJ1JkEe0PTnnsbGewGkyS8EsbxWaKbslA5qZtP/WRo04/3vxu/2jLWKU9jLgRKE DwOOp15G7W8HNJS7w6NjlcwCQigPthWDHcrQhKnZI4KtaL9lha0jEqiT2gycbm9rSWbZ Ilms5DUa69GiPo+S0ZV3XBu6pcjmi6kKn3vgRr5rIkRtif752kVm34WCKubihGL6Y7lE ODVQ==
X-Received	by 10.224.24.134 with SMTP id v6mr21675676qab.88.1401999127779; Thu, 05 Jun 2014 13:12:07 -0700 (PDT)
Date	Thu, 05 Jun 2014 16:12:05 -0400
From	R Johnson <ps16thypresenceisfullnessofjoy@gmail.com>
User-Agent	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version	1.0
To	python-list@python.org
Subject	How to use SQLite (sqlite3) more efficiently
Content-Type	text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding	7bit
X-Antivirus	avast! (VPS 140605-0, 06/05/2014), Outbound message
X-Antivirus-Status	Clean
X-Mailman-Approved-At	Thu, 05 Jun 2014 22:21:30 +0200
X-BeenThere	python-list@python.org
X-Mailman-Version	2.1.15
Precedence	list
List-Id	General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe	<https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive	<http://mail.python.org/pipermail/python-list/>
List-Post	<mailto:python-list@python.org>
List-Help	<mailto:python-list-request@python.org?subject=help>
List-Subscribe	<https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups	comp.lang.python
Message-ID	<mailman.10764.1401999691.18130.python-list@python.org> (permalink)
Lines	11
NNTP-Posting-Host	2001:888:2000:d::a6
X-Trace	1401999691 news.xs4all.nl 2970 [2001:888:2000:d::a6]:55986
X-Complaints-To	abuse@xs4all.nl
Xref	csiph.com comp.lang.python:72758

Show key headers only | View raw

I forgot to mention that the scripts Peter pointed to used REPLACE 
instead of INSERT OR REPLACE. The SQLite documentation says that REPLACE 
is an alias for INSERT OR REPLACE provided for compatibility with other 
SQL database engines. Is there a preference for one or the other?

I had changed my code from using INSERT OR REPLACE to using REPLACE 
(including my new sample), but since then changed it back. I don't care 
about compatibility with other database engines, and INSERT OR REPLACE 
seems more logical to me, since REPLACE sounds like a synonym for UPDATE.

-- Timothy

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

Thread

How to use SQLite (sqlite3) more efficiently R Johnson <ps16thypresenceisfullnessofjoy@gmail.com> - 2014-06-05 16:12 -0400

csiph-web