in reply to A First CPAN Odyssey

On a related thread, I'm curious as to how I should go about testing interactions with a database on a user's system. It would be very rude for the testing procedures of my module to carelessly stomp on the database residing on someone's machine. What precautions and paradigms should I employ so as both to thoroughly test my module on the user's machine and avoid trashing his environment? I've read horror stories of hapless users having rogue modules smash their data, and I'd rather not be a purveyor of such a module.
Require DBI::SQLite as a dependency and run your own database, or perhaps DBD::Anydata.

Replies are listed 'Best First'.
Re^2: A First CPAN Odyssey
by jZed (Prior) on Jun 23, 2004 at 00:59 UTC
    Or use DBD::DBM - it comes with DBI (1.42 and above) so (evenutally) you can count on users already having it.
[reply]
Re^2: A First CPAN Odyssey
by clscott (Friar) on Jun 23, 2004 at 02:23 UTC

    Re: Testing

    You should look at how Class::DBI does it's testing using SQLite.
    --
    Clayton
[reply]
Re^2: A First CPAN Odyssey
by skyknight (Hermit) on Jun 22, 2004 at 23:34 UTC
    Ah, that is an excellent suggestion. Thanks for the idea.
[reply]

In Section Meditations