When running propel-gen diff, you'll find that the program is complaining about missing adapter to initiate DB connection.
This happens because during that operation, self::configuration is NULL, but I don't know where is the place where is being set during the migration operation.
http://stackoverflow.com/questions/17179364/propel-postgresql-migration-unable-to-find-adapter. He put a fix but it is not the right way to do it, so if you can give us some guidance about where should be the place to look for it would be very helpful
I'm experiencing the same problem. Running with pgsql 9.1 configuration and latest 1.7.*@dev. release of propel. The configuration self::$configuration file at this point returns NULL. I'm about to apply the dirty solution given in the stackoverflow post above, but I'm really eager to find a more satisfying solution. I'm really curious on how it can find the correct database name, but fails to detect the driver from the buildtime-/runtime-configuration file (both identical).
I found out the following: The adapter is supplied in the $conparams argument (method initConnection). Adding the following line to Propel.php solved all my problems. This still might not be the prettiest solution there is, but it most certaily works for me.
Around line 650 in Propel.php:
Change $adapter = self::getDB($name); into $adapter = isset($conparams['adapter']) ? DBAdapter::factory($conparams['adapter']) : self::getDB($name);
$adapter = self::getDB($name);
$adapter = isset($conparams['adapter']) ? DBAdapter::factory($conparams['adapter']) : self::getDB($name);
Is anyone going to fix this issue?
fix seems to be jh-ism-online-webmaster@846640a, PR with unit test welcome
+1 fixed when used jh-ism-online-webmaster@846640a
Will this ever be merged into a 1.x release? This really breaks my composer friendly installs.