Smylers wrote:
> It sounds scary to me. If I'm just installing a Perl module from Cpan
> on a newly installed OS, which happens to still have default DB
> connection permissions, I wouldn't expect the module's tests to start
> making use of the DB without asking.
Of course, a module author can do that already, he just has to reinvent
the wheel to do it. He can also email your password file to his Russian
chums if you sudo perl -MCPAN ... (which far too many of us, me
included, do).
> Further, if the module install fails the database may be left behind.
Having a well-known module specifically for creating, accessing, and
tearing down the test database, written carefully and maintained,
instead of people just hacking up their own nasty solutions to the
problem whenever they need it - this will *reduce* the chances of that
happening. End result - less cruft left on your system *and* better
testing for databasey modules.
--
David Cantrell | Cake Smuggler Extraordinaire
NANOG makes me want to unplug everything and hide under the bed
-- brian d foy
