In this very script you make a call to DBI.

These calls you are using add very little to DBI's capabilities.

If you're looking to get out of writing as much SQL, I'd recommend looking up DBIx::Class or Class::DBI in CPAN.

I'm not trying to dog on your work. I'd just like to suggest that you explain why this API is useful beyond DBI which already contains full error handling.

The reason this is usefull to me is that if (and I know this is a long shot) there is ever a huge update to Perl's DBI, or we decide to use another solution, I do not have to rewite the nearly 300 perl scripts that I have running off of it. All I would have to do it update the one file. Also it saves me some time in writing:

or &handle_error ("Can't prepare statement '$sql': $DBI::errstr")

or something of the sort after every time I need to run a sql statement.

API for DBI is stable and won't change in future. If you need to die on error, there is RaiseError parameter (both on connect and for every command).

---
Sasha Chorny, http://chorny.net