On Tue, Sep 23, 2003 at 04:47:10PM -0700, Michael A Nachbaur wrote: > > As it stands, it explicitly builds BerkeleyDB files but, I don't see why it > shouldn't be able to write to arbitrary back-ends or, as the case may be, > plain-old hashes. > > > Unless I misinferred its purpose, I think something like > > DBIx::Results::HashView would be more appropriate. > > That sounds like a good name. I'll go ahead with that one, unless anyone else > has anything else to suggest?
I don't like the idea of a DBIx::Results::* namespace. >From what you've said I'd suggest DBIx::Export2HashDB Tim. p.s. I agree with Aristotle's comments about the module config being driven by perl data structures so it's reusable without forcing users to generate config files.
