That would be fine. I was thinking in terms of supporting data formats that can't be queried, though why DBD is sort of not an issue here. Though AnyData.pm, I haven't looked at the source, I'm not sure if Jeff wants to add these misceleneous data structures. Also...
I just added an event driven interface to DBIx::Dump, which allows to define event handlers and due on the fly transformations/formatting before outputting. Not sure about the AnyData interface and if it will allow for such additions without much reprogramming. Jeff??? Ilya -----Original Message----- From: [EMAIL PROTECTED] To: Sterin, Ilya Sent: 10/3/02 2:44 PM Subject: Re: Uploaded to CPAN: DBIx::Dump The following message is a courtesy copy of an article that has been posted to perl.dbi.users as well. >>>>> "Ilya" == Ilya Sterin <[EMAIL PROTECTED]> writes: Ilya> DBIx::Dump allows to dump DBI result set into a variety of formats like Ilya> Excel, CSV, XML, etc... Ilya> Right now, it only dumps to Excel, tomorrow's release will dump into CSV as Ilya> well, then sometime this week it will dump into XML... How is this different from what DBD::AnyData can do? Maybe the two of you should get together and merge efforts, or maybe you can just take over maintenance? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
