A couple of weeks ago i made a change which i'm not at all happy with. The problem is to fetch objects for a given class in the database, without being propel nor doctrine specific. Such a method is needed in the object helpers.
The new solution is as follows: all model classes will have a default connection, as is the case now with the propel peer classes. That default connection will be a constant "DATABASE_NAME" of the class. I modified SfObjectBuilder accordingly. This is much more robust and more logical than the previous solution. It also allows to use both propel and doctrine in the same project. People will have to rebuild their model when they svn update. If there is no objection i will revert my previous changes and commit the new ones. (functional tests pass provided that one adds the DATABASE_NAME as explained above). == Olivier Le 5 oct. 06 à 16:36, Olivier a écrit : > I commited my changes to totally separate symfony from propel. All > the tests pass with those changes. > > There is a mild "BC break" for people having no connection named > "propel". Those people will have to specify a "default_database" > default connection in settings.yml. If they are using propel, any > propel connection will do. I hope it's an acceptable price to pay > for the separation of symfony and propel. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs -~----------~----~----~----~------~----~------~--~---
