DML drivers: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Moodle_2.0}}Previous versions were using adodb abstraction partially | {{Moodle_2.0}}Previous versions were using adodb abstraction partially encapsulated by old DML api. The database drivers are now fully separated from the rest of code and it is even possible to create new native drivers that do not rely on adodb abstraction anymore. | ||
At present there are two sample native drivers - mysql and pgsql. The benefits are: | |||
* more optimised and probably faster | |||
* consume less memory | |||
* better possibility to improve logging, debugging, profiling | |||
* smaller code & easier to fix and maintain | |||
* and more | |||
TODO: add more info here | |||
TODO: add more info here | |||
Revision as of 23:13, 24 November 2008
Moodle 2.0
Previous versions were using adodb abstraction partially encapsulated by old DML api. The database drivers are now fully separated from the rest of code and it is even possible to create new native drivers that do not rely on adodb abstraction anymore.
At present there are two sample native drivers - mysql and pgsql. The benefits are:
- more optimised and probably faster
- consume less memory
- better possibility to improve logging, debugging, profiling
- smaller code & easier to fix and maintain
- and more
TODO: add more info here
See also
- DML functions: Where all the functions used to handle DB data (DML) are defined.
- DML exceptions: New DML code is throwing exceptions instead of returning false if anything goes wrong
