inside ProjectConfiguration?.class.php in a symfony project, using something like:
public function configureDoctrine(Doctrine_Manager $manager) {
$manager->setAttribute(Doctrine::ATTR_MODEL_LOADING, Doctrine::MODEL_LOADING_CONSERVATIVE);
$manager->setAttribute(Doctrine::ATTR_VALIDATE, Doctrine::VALIDATE_ALL);
$manager->setAttribute(Doctrine::ATTR_EXPORT, Doctrine::EXPORT_ALL);
}
causes strange behavior with ./symfony doctrine:build-schema. The offending line seems to be:
$manager->setAttribute(Doctrine::ATTR_MODEL_LOADING, Doctrine::MODEL_LOADING_CONSERVATIVE);
namely, the problems are as follows:
- without removing the lib/model/doctrine/base directory, the old versions of the Base classes were used instead of the tmp directory derived files to generate the yml.
- database changes were not properly recognized in the schema.yml.
- autoloading exceptions are thrown if ../base is removed in an attempt to "force" doctrine to see the new DB layout
is this expected behavior?
