Re: How do I trap DBI errors?




megapode@xxxxxxxxx wrote:

One of the requirements, of course, is that if the program cannot
connect to or cannot update the audit trail table then the program
should generate an error condition and not accept the file that is
being sent.

snip!

And thanks for the off-list reply. It seems that checking $DBI::errstr
does the trick.

.



Relevant Pages

  • Re: scanf problem with intaking a string *PLS. HELP*
    ... snip ... ... even though the function interface itself doesn't provide ... well use getc. ... error condition. ...
    (comp.lang.c)
  • Re: the mystery of
    ... aesthetics. ... reserved for an error condition. ... I wouldn't dream of using it for that purpose. ...
    (comp.lang.c)
  • Re: data and script in same location, how to write it down
    ... but I dislike the error messages that say ... Or maybe I have worked with too many English majors. ... You are talking about a microsecond interval between the error being detected and the message being displayed, of course the error condition no longer exists, the program just died! ...
    (perl.beginners)
  • Re: Logging database changes
    ... transaction journaling. ... The purpose of an audit trail is to rapidly ... in some circumstances and I do use it as well as the audit file. ...
    (comp.databases.pick)
  • Re: deleting ldap users question
    ... > understand why my code is not deleting the relevant entries. ... check for an error condition like they do in the example, ...
    (perl.beginners)