XMLDB creating new DDL functions - pre 2.0: Difference between revisions
No edit summary |
m (→See also) |
||
| Line 12: | Line 12: | ||
== See also == | == See also == | ||
* [[XMLB List of functions to create|List of | * [[XMLB List of functions to create|List of functions to create]]: The list of functions to be created from scratch. Used to follow the progress and its status. | ||
* http://www.hitsw.com/xml_utilites/: One online XML-DTD-Schema conversor. | * http://www.hitsw.com/xml_utilites/: One online XML-DTD-Schema conversor. | ||
[[Category:XMLDB]] | [[Category:XMLDB]] | ||
Revision as of 16:34, 13 August 2006
XML database schema > Roadmap > XMLDB Creating new DDL functions
Justification
Before Moodle 1.6, all the DB install and upgrade was developed twice (once to handle MySQL installations and another to handle PostgreSQL installations). This approach, although working, has caused some headaches in the past, mainly because it was really difficult to keep both lines of development 100% on sync. Some developers do they work against one RDBMS and it was complex to develop to the other one (two test environments, skills on both databases, slower development cycle...). And all this was happening with only two supported RDBMS!
One of the main objectives of Moodle 1.7 is to extend the the number of supported RDBMS to other flavours (more exactly, to Oracle and MSSQL). And the old approach (one line of development for each DB) could become an absolute nightmare.
Implementation
See also
- List of functions to create: The list of functions to be created from scratch. Used to follow the progress and its status.
- http://www.hitsw.com/xml_utilites/: One online XML-DTD-Schema conversor.
