That's a new one to me. I use perl/DBI also and my scripts just ignore
errors w/o any error trapping. Maybe my defaults are set to ignore
errors. I only trap errors when I there's a possibility of catastrophic
failure. (Example, DB is down -- SELECT * FROM zzz returns an error so
the row count is 0 -- page looks normal except there's no content versus
some generic apache error message.)
Davis, Sean (NIH/NHGRI) wrote:
> Point taken. However, in a perl/DBI setting, the program does die unless I
> explicitly trap the error, etc. So, it is a convenience, true enough, but
> not an issue that I had to deal with in MySQL, so just thought I would ask.
