Re: Intercepting DBD:ODBC errors
zzapper <[email protected]>
| Newsgroups | gmane.comp.db.mysql.perl |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 11 Apr 2005 12:45:51 -0400, wrote: >On Mon, 2005-04-11 at 16:57 +0100, zzapper wrote: >> Certain types of mysql error seem to directly output their error message and thus break break my >> scripts before the error can be intercepted at the perl level and dealt with gracefully. >> >> Ideas? > >I guess you mean the DBI module(?). See the DBI(3) manual page, >PrintError in the ATTRIBUTES COMMON TO ALL HANDLES section: > > By default, "DBI->connect" sets "PrintError" "on". > >-- >Garry Williams, +1 678 565-4579 Whoops I also had it specifically switched on, but what's the best policy have it on for testing OR leave it off and always test at the Perl level? -- MySQL Perl Mailing List For list archives: http://lists.mysql.com/perl To unsubscribe: http://lists.mysql.com/[email protected]