FWIW, a couple of years ago I wrote an implementation of a multi-index container with an ORM-ish interface (http://norman.readthedocs.org/en/latest/), more for my own amusement than any practical purposes.  However, I found that in my work the applications were actually rather limited and generally better served by sqlalchemy + appropriate db, or pandas (depending on use case).  I haven't touched the code in quite a while and there may be some bugs that I never discovered, but it might still be of some use.

David

On Wed, Dec 3, 2014 at 3:10 PM, SF Markus Elfring <elfring@users.sourceforge.net> wrote:
> Sorting on demand would be way too slow but it doesn't need to be in
> a database either - it can be reconstructed from an event stream,
> and running a DB server is extra ops.

I am looking also for ways to omit persistent storage for a specific
data processing task. How often will simple index management be sufficient
for some software applications?


> Using an in-memory DB like SQLite is an unnecessary extra layer.

How many in-memory data bases can be reused by the Python software infrastructure?
Would you like to point any more class libraries out?

Regards,
Markus
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/