my life

I upgraded to a newer version of Symfony today (v1.0.6) and had a hell of time getting the trivial task of connecting to the database working.

I was able to obtain a connection, by doing


$databaseManager = new sfDatabaseManager();
$databaseManager->initialize();
$con = $databaseManager->getDatabase('propel');


but that’s not the ideal way, and not the way symfony gets the database handle.


$con = Propel::getConnection('propel');
on the otherhand throws an excpetion.

First, it was important to check that config/schema.xml is correct

All that was good. But for some reason sfPropelAutoload was not geting loaded.

If I manually included it


include './lib/symfony-1.0.7/lib/addon/propel/sfPropelAutoload.php'It was clearly listed in the autoloader.yml


it would work, but still not desirable.

The following was in my autoloader config,

but it still wouldn’t load my sfPropelAutoload class. Adding the following made it start working…

I was getting this error today on a new Symfony project. The problem was that I had defined the schema in the schema.xml file, but there was a conflicting schema.yml file that sat empty. Removing (