IN THIS CHAPTER
Flagging error conditions
Branching to error-handling code
Determining the exact nature of an error
Finding out which DBMS generated an error condition
Wouldn’t it be great if every application you wrote worked perfectly every time? Yeah, and it would also be really cool to win $314.9 million playing Powerball. Unfortunately, both possibilities are equally unlikely to happen. Error conditions of one sort or another are inevitable, so it’s helpful to know what causes them. SQL’s mechanism for returning error information to you is the status parameter (or host variable)
SQLSTATE. Based on the contents of
SQLSTATE, you can take different actions to remedy the error condition.
For example, the
WHENEVER directive enables you to take a predetermined action whenever a specified condition (if
SQLSTATE has a non-zero value, for example) is met. You can also find detailed status information about the SQL statement that you just executed in the diagnostics area. In this chapter, I explain these helpful error-handling facilities and how to use them. ...