DML exceptions: Difference between revisions
David Mudrak (talk | contribs) (→dml_read_exception: fix read -> write) |
Dev Docs Bot (talk | contribs) m (Update migration status and path) |
||
Line 1: | Line 1: | ||
{{Template:Migrated|newDocId=/docs/apis/core/dml/exceptions}} | |||
{{Moodle_2.0}}In previous versions problems in database calls were ignored by default. | {{Moodle_2.0}}In previous versions problems in database calls were ignored by default. | ||
Revision as of 14:03, 13 June 2022
Important:
This content of this page has been updated and migrated to the new Moodle Developer Resources. The information contained on the page should no longer be seen up-to-date. Why not view this page on the new site and help us to migrate more content to the new site! |
Moodle 2.0
In previous versions problems in database calls were ignored by default.
Overview
Defined in lib/dmllib.php for now.
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_write_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.