DB layer 2.0 implementation plan

Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.

Milestones

What is done:

1. API should be stable, tested during conversion of several parts or moodle

2. $db-> references are gone

3. direct adodb function calls should be all gone (except auth and enrol)

4. some functions from dmllib are deprecated/removed

5. old ddllib function are not used at all now

6. XMLDB editor should fully work now

7. BC compatible 100$

1. mssql and ora related work

2. use of adodb in enrol and auth plugins

3. functional unit tests (own-db and multi-db)

4. logging/profiling/exceptions

5. xmldb public API refactoring

6. install

7. BC compatible 100$

8. In general everything titled as "M2" in the Bug Tracker.

1. Needs to be detailed in dmllib 2.0 migration docs.

2. Tasks between May28th and June 11th

3. API should be available in the phpdocs site

4. BC compatible 100$

5. In general everything titled as "M3" in the Bug Tracker.

1. BREAKAGE with old code.

2. Documentation finished (Docs (examples, architecture, migration guide...), PHP Docs).

3. In general everything titled as "M4" in the Bug Tracker.

1. Needs good documentation for developers

2. Will be huge but useful

3. Always try to be able to run tests from cli script (apart from UI) to be able to execute them daily and report status in some URL (html output).