Dylan Reinhardt wrote at 2003-1-15 22:05 -0800:
... It was designed to simplify the process of storing, optimizing, and extracting complex (i.e. "Pythonish") data so that it isn't necessary to translate back and forth between OO-style data and SQL-style data. It's basically a big mapping with recordset caching, selection/aggregation mechanisms, data typing and multi-level sorting built in.
I wouldn't say it's optimal for *all* kinds of data, but it sure seems to work well at organizing the kind of data you might kick up in a mid-size business app. My last several apps don't have a scratch of SQL in them anywhere. :-)
Anyway, it's my baby so I've lost perspective on it and don't really have any idea whether this is a redundant and/or stupid idea or if this is the kind of thing I should be releasing to the community. Some comments and perspective on this would be greatly appreciated. I have done something similar.
From your description, it seems that your solution is more versatile.
Thus, it might be interesting... Dieter