MDL-30147 do not rely on dml exception type outside of dml layer

The trouble is that dml driver methods (insert, update, select) are not guaranteed to return the same exception class for various db problems and coding style issues. The recommended practice is to catch dml_exception only.
This commit is contained in:
Petr Skoda 2011-11-12 17:39:19 +01:00
parent c04e80e328
commit 69ac5d478f
5 changed files with 14 additions and 14 deletions

View file

@ -91,7 +91,7 @@ class dml_sessionwait_exception extends dml_exception {
}
/**
* DML read exception - triggered by SQL syntax errors, missing tables, etc.
* DML read exception - triggered by some SQL syntax errors, etc.
*/
class dml_read_exception extends dml_exception {
/** @var string */
@ -185,7 +185,7 @@ class dml_missing_record_exception extends dml_exception {
}
/**
* DML write exception - triggered by SQL syntax errors, missing tables, etc.
* DML write exception - triggered by some SQL syntax errors, etc.
*/
class dml_write_exception extends dml_exception {
/** @var string */