On Thursday, I was trying to run some unit tests and as I don't want to reload all my dev fixtures which are more complex than my test fixtures, I want to create 3 databases and switch between them depending of the environnment, like in RoR. But unfortunately, the way Propel is setting up make it impossible. Another reason to switch to Doctrine, when it has reached suffisant maturity !
Nautile On 22 juil, 22:00, "Luciano A. Andrade" <[EMAIL PROTECTED]> wrote: > it will a good idea to make a propel.yml that can define the > propel.ini, much like the schema.yml > > On 7/20/07, Frank Stelzer <[EMAIL PROTECTED]> wrote: > > > > > This is a propel problem. The database settings in databases.yml are > > needed for runtime stuff, the settings in the propel.ini for the > > propel generator (for all symfony propel-* tasks). Propel needs for > > this generator a properties like file and so it could not be used > > with the yml file. > > > Look at the sfDoctrine plugin, there you define your database > > settings only at one place, because doctrine needs no special > > settings file. > > > - Frank > > > Am 20.07.2007 um 18:56 schrieb Thierry: > > > > why are we specifying database connections in both databases.yml and > > > propel.ini? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
