Development:DML exceptions: Difference between revisions
From MoodleDocs
No edit summary |
|||
Line 4: | Line 4: | ||
[[Image:Dml_exceptions.png]] | [[Image:Dml_exceptions.png]] | ||
=== | ===dml_connection_exception=== | ||
Thrown when can not connect to database for any reason. | |||
===dml_read_exception=== | ===dml_read_exception=== | ||
Problem occurred during reading from database. Originally indicated be returning ''false'' - this value was often confused with ''false'' return value meaning ''not found''. | |||
===dml_read_exception=== | ===dml_read_exception=== | ||
Problem occurred during writing to database. Originally indicated be returning ''false''. | |||
==See also== | ==See also== |
Revision as of 17:21, 27 November 2008
Template:Moodle 2.0In previous versions problems in database calls were ignored by default.
Overview
dml_connection_exception
Thrown when can not connect to database for any reason.
dml_read_exception
Problem occurred during reading from database. Originally indicated be returning false - this value was often confused with false return value meaning not found.
dml_read_exception
Problem occurred during writing to database. Originally indicated be returning false.
See also
- Exceptions: General guidelines for using of exceptions in Moodle 2.0
- DML functions: Where all the functions used to handle DB data. (DML) are defined.
- DDL functions: Where all the functions used to handle DB objects (DDL) are defined.