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


Groups > comp.lang.python > #26745 > unrolled thread

Re: dbf.py API question

Started byEd Leafe <ed@leafe.com>
First post2012-08-07 20:10 -0500
Last post2012-08-07 20:10 -0500
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: dbf.py API question Ed Leafe <ed@leafe.com> - 2012-08-07 20:10 -0500

#26745 — Re: dbf.py API question

FromEd Leafe <ed@leafe.com>
Date2012-08-07 20:10 -0500
SubjectRe: dbf.py API question
Message-ID<mailman.3073.1344388628.4697.python-list@python.org>
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.
> 
> 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=True) 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


[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web