[Zope] data manager object - seeking comments

[Dylan Reinhardt]

Howdy Zopers,

The last year or so, I've been making extensive use of a drop-in data 
manager class in my products.  It started off as a caching database 
connector and at some point I decided it was a better tool without the 
database layer. :-)

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.

Please respond directly & I'll update the list with whether or not I'll be 
making a release announcement.

Thanks in advance for any (seriously, any) feedback,

Dylan