. */ /** * class Doctrine_Import_Schema * * Different methods to import a XML schema. The logic behind using two different * methods is simple. Some people will like the idea of producing Doctrine_Record * objects directly, which is totally fine. But in fast and growing application, * table definitions tend to be a little bit more volatile. importArr() can be used * to output a table definition in a PHP file. This file can then be stored * independantly from the object itself. * * @package Doctrine * @category Object Relational Mapping * @link www.phpdoctrine.com * @license http://www.opensource.org/licenses/lgpl-license.php LGPL * @version $Revision: 1838 $ * @author Nicolas BĂ©rard-Nault * @author Jonathan H. Wage */ abstract class Doctrine_Import_Schema { /** * parse * * Function to do the actual parsing of the file * * @param string $schema * @return void * @author Jonathan H. Wage */ abstract function parse($schema); /** * Parse the schema and return it in an array * * @param string $schema * @access public */ abstract function parseSchema($schema); /** * importSchema * * A method to import a Schema and translate it into a Doctrine_Record object * * @param string $schema The file containing the XML schema * @param string $directory The directory where the Doctrine_Record class will * be written * @access public */ public function importSchema($schema, $directory) { $builder = new Doctrine_Import_Builder(); $builder->setTargetPath($directory); $array = $this->parseSchema($schema); foreach ($array as $name => $properties) { $options['className'] = $properties['class']; $options['fileName'] = $directory.DIRECTORY_SEPARATOR.$properties['class'].'.class.php'; $columns = $properties['columns']; $builder->buildRecord($options, $columns, array()); } } }