One thing that was not mentioned in the answers you've already had, is that once you've implemented the DBI/DBD interface, it is normally very easy to change what underlying database engine your application will use. If you're able to avoid any database calls that are specific to a certain database and only use the 'smallest common denominator' you may be able to change the underlying database by changing one single line in your Perl code.

You will, of couse, OTOH have to install the new database engine, but that's out of scope for your Perl application. And this is exactly my point. Using DBI/DBD, and taking care not to call any 'obscure' database functionality, you may make your application almost 100% unaware of what database you're using.

Which is a Good Thing (TM used with permission).

f--k the world!!!!
/dev/world has reached maximal mount count, check forced.