Alzabo::Exceptions - Creates all exception subclasses used in Alzabo.
Using this class creates all the exceptions classes used by Alzabo (via the
Exception::Class class). If the environment variable 'ALZABO_DEBUG' is true, then it will turn on stacktrace generation for all the exception classes.
Exception::Class for more information on how this is done.
This is the base class for all exceptions generated within Alzabo (all exceptions should return true for
$@->isa('Alzabo::Exception')except those that are generated via internal Perl errors).
Base class for cache-related exceptions.
An attempt was made to operate on a row that had been deleted in the cache. In this case there is no point in attempting further operations on the row, as it is no longer in the database.
An attempt was made to operate on a row that had been expired in the cache. The row will refresh itself before returning this exception so it may be desirable to attempt the operation that caused this error again.
An error occured while accessing a database. See
Alzabo::Driverfor more details.
An attempt to eval something returned an error.
Alzabo was asked to do something logically impossible, like retrieve rows for a table without a primary key.
An attempt was made to fetch data from the database with a primary key that does not actually exist in the specified table.
This exception is thrown when there is a problem with the parameters passed to a method or function. These problems can include missing parameters, invalid values, etc.
A rule for the relevant RDBMS was violated (bad schema name, table name, column attribute, etc.)
An insert/update/delete was attempted that would violate referential integrity constraints.
An error thrown when there is an attempt to generate invalid SQL via the Alzabo::SQLMaker module.
Some sort of system call (file read/write, stat, etc.) failed.
A virtual method was called. This indicates that this method should be subclassed.
Dave Rolsky, <email@example.com>