On Tuesday 23 September 2003 04:09 pm, A. Pagaltzis wrote: > * Michael A Nachbaur <[EMAIL PROTECTED]> [2003-09-23 22:53]: > > It is essentially a Perl script that takes a series of SQL > > statements and outputs the results to a BerkeleyDB (with > > various indexes created, on a configurable basis). > <snip> > Instead, if I understood your description correctly, it actually > performs the SQL queries it gets against a database. Probably > using DBI. Then the most fitting already existent TLN for it is > probably DBIx::.
Very true. > As for the descriptive name, well, it exports a query result into > a hash structure. Does it export the results of multiple queries? Yes, it exports the result of multiple queries, right now, as defined in a config file managed by Config::General. > Is it inherent to the module that results go into a tied DBM > hash (or multiple ones) or could it also just use plain hashes? > And does it have a BerkeleyDB or would another DBM engine > suffice? 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? -- /* Michael A. Nachbaur <[EMAIL PROTECTED]> * http://nachbaur.com/pgpkey.asc */ "OK, so ten out of ten for style, but minus several million for good thinking, yeah? "
