Nomenclature: red text = still undecided.

Agenda:

• From previous meeting + docs comments:

1. moodle unit tests (using dmllib stuff)
2. exercise and lams - cut them loose (don't worry about them)
   
3. journal and workshop (will need to convert them for 2.0)
   

• Review OOP:

1. Discuss Interface proposa
2. Quick review of requirements
3. Quick review of previous meeting - OOP section

• Implementation details, determine 5 milestones with times (each Milestone 1 META bug)

1. M1: initial commit
2. M2: 4 DBs passing all tests
3. M3: core stuff, pre magic_quotes off tasks
4. M4: BREACKAGE: big hacking, post magic_quotes off tasks
5. M5: Moodle tests using real & mockup dmllib (HEAD)

• Documentation:

1. API=>OOP quick tour and Examples
2. big hack=>Migration (very important!)
3. tests=>Testing

• Other:

1. Problems
2. Ideas and comments
3. Next meeting

Summary:

OOP:

• database instances database manager that will use generators (DDL stuff). Only one default manager to be used by all drivers (although can be overriden). The database manager will have, as public API, all current methods in ddllib.php. All this stuff goes to lib/ddl.
• discussion about public/private attributes and public API (moodle_database and moodle_database_manager).
• going to use __construct instead of class names as constructors (Eloy is alone against that).
• exception are a must. they will be thrown up to one global error handling fallback (see Mahara) until modules start doing its job handling exceptions.
• placeholders publicy supported only will be ? and :names. Any DB requiring different ones (PostgreSQL $1...) will perform the conversion as needed (internally).
• bound query emulation to work around some pgsql limitations

Tests:

• table prefix is separated so it's easy to create moodle_database instances with different prefixes.
• able to test execute test agains multiple DBs by:

1. Having some interface in admin to define them
2. Make tests happen against all them
3. If no alternate DBs are defined, tets default to current one (config.php one)

• will go to dml/simpletest and ddl/simpletest

Logging:
Start using one own table (instead of current adodb one). Will measure total execution time per statement.

Milestones:

• M1: (BC compatible) initial commit (HEAD). (May 15th - 23:00 GMT +1 +DST - after next meeting)
• M2: (BC compatible) 4 DBs passing all tests (HEAD) (May 27th)
• M3: (BC compatible) core stuff, pre magic_quotes off tasks (HEAD) (starting on June 11th, to June 24th)
• M4: (BREAKAGE!) big hacking, post magic_quotes off tasks (HEAD, BRANCH, PATCH??) (starting on June 11th to June 24th)
• M5: Moodle tests using real & mockup dmllib (HEAD) (starting on May 27th, to ....)

Next Meeting:

May 15th 2008 - 10:00 EU Time