Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #26410 > unrolled thread
| Started by | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| First post | 2012-08-02 08:55 -0700 |
| Last post | 2012-08-02 08:55 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
dbf.py API question Ethan Furman <ethan@stoneleaf.us> - 2012-08-02 08:55 -0700
| From | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| Date | 2012-08-02 08:55 -0700 |
| Subject | dbf.py API question |
| Message-ID | <mailman.2878.1343922090.4697.python-list@python.org> |
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. Thoughts? ~Ethan~
Back to top | Article view | comp.lang.python
csiph-web