Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <ed@leafe.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.001
X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'languages,': 0.04; 'desired.': 0.07; 'table.': 0.07; 'subject:question': 0.08; 'sqlite': 0.09; 'surrounded': 0.09; 'cc:addr:python-list': 0.10; 'language,': 0.11; 'aug': 0.13; 'resulting': 0.13; 'colons': 0.16; 'disk.': 0.16; 'in-memory': 0.16; 'paradigms': 0.16; 'pythonic': 0.16; 'subject:API': 0.16; 'tempted': 0.16; 'wrote:': 0.17; 'expanded': 0.17; 'memory': 0.18; 'cc:2**0': 0.23; "i've": 0.23; 'feature': 0.24; 'cc:addr:python.org': 0.25; 'header:In-Reply- To:1': 0.25; 'wondering': 0.26; 'am,': 0.27; 'converting': 0.27; 'disk': 0.27; 'feature,': 0.29; "i'm": 0.29; 'table': 0.35; 'but': 0.36; 'method': 0.36; 'should': 0.36; 'charset:us-ascii': 0.36; 'subject:: ': 0.38; 'possible.': 0.38; 'instead': 0.39; 'received:192': 0.39; 'where': 0.40; 'received:192.168': 0.40; 'header:Message-Id:1': 0.62; 'situation': 0.62; 'results': 0.65; 'furman': 0.84; 'ethan': 0.91
Subject: Re: dbf.py API question
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Ed Leafe <ed@leafe.com>
In-Reply-To: <501AA304.3090000@stoneleaf.us>
Date: Tue, 7 Aug 2012 20:10:07 -0500
Content-Transfer-Encoding: quoted-printable
References: <501AA304.3090000@stoneleaf.us>
To: Ethan Furman <ethan@stoneleaf.us>
X-Mailer: Apple Mail (2.1278)
Cc: Python <python-list@python.org>
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://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: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.3073.1344388628.4697.python-list@python.org>
Lines: 23
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1344388628 news.xs4all.nl 6901 [2001:888:2000:d::a6]:60696
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:26745

On Aug 2, 2012, at 10:55 AM, Ethan Furman wrote:

> SQLite has a neat feature where if you give it a the file-name of =
':memory:' the resulting table is in memory and not on disk.  I thought =
it was a cool feature, but expanded it slightly: any name surrounded by =
colons results in an in-memory table.
>=20
> I'm looking at the same type of situation with indices, but now I'm =
wondering if the :name: method is not pythonic and I should use a flag =
(in_memory=3DTrue) when memory storage instead of disk storage is =
desired.

	When converting from paradigms in other languages, I've often =
been tempted to follow the accepted pattern for that language, and I've =
almost always regretted it.

	When in doubt, make it as Pythonic as possible.


-- Ed Leafe