The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

<!--  Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->

<HTML>
<HEAD>

<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
 <TITLE>Handling errors the smart way</TITLE> 
</HEAD>

<BODY     >

<CENTER>
<TABLE WIDTH=100%> 
     <TR> <TD WIDTH=100% ALIGN=CENTER>
         <A HREF="sld001.htm">First</A>&nbsp;&nbsp;
         <A HREF="sld043.htm">Previous</A>&nbsp;&nbsp;
         <A HREF="sld045.htm">Next</A>&nbsp;&nbsp;
         <A HREF="sld102.htm">Last</A>&nbsp;&nbsp;
&nbsp;&nbsp;         <A HREF="index.htm">Index</A>&nbsp;&nbsp;
         <A HREF="dbi.perl.org">Home</A>&nbsp;&nbsp;
         <A HREF="tsld044.htm">Text</A>&nbsp;&nbsp;
     </TD> </TR>
     <TR> <TD WIDTH=100% ALIGN=CENTER>
         <IMG SRC="img044.gif" usemap="#Objmap" WIDTH=800 HEIGHT=600 BORDER=0>
     </TD> </TR>
</TABLE>
<P>Slide 44 of 102</P>
</CENTER>
<!-- <UL>
<H2>Handling errors the smart way</H2>
</UL></P>
<P><UL>
<LI><H2>Setting RaiseError make the DBI call die for you
</H2>
<UL>
<LI>
</UL></UL><UL>
<LI><H2>For simple applications immediate death on error is fine
</H2>
<UL>
<LI>The error message is usually accurate and detailed enough
<LI>Better than the error messages some developers use!
<LI>
</UL></UL><UL>
<LI><H2>For more advanced applications greater control is needed, perhaps:
</H2>
<UL>
<LI>Correct the problem and retry
<LI>or, Fail that chunk of work and move on to another
<LI>or, Log error and clean up before a graceful exit
<LI>or, whatever else to need to do
<LI>
</UL></UL><UL>
<LI><H2>Buzzwords:
</H2>
<UL>
<LI>Need to catch the error exception being thrown by RaiseError
<LI>
</UL></UL><UL>
<H2>.</H2>
</UL></P>
<P>  -->
</Body>
</HTML>