Well doctrine bundle uses the standard Doctrine stuff, but it applies the fixed way of autodetecting. This makes it so hard to work with it in all the special circumstances.
I'll patch the code and make a pull request to you and /cc it to jonathan. Benjamin On Thu, 09 Dec 2010 17:53:23 +0100, Fabien Potencier <[email protected]> wrote: > On 12/9/10 5:44 PM, Benjamin Eberlei wrote: >> yes. > > That's excellent then. I'm all for it. > > The less code we have in the Doctrine bundle, the better. Doctrine > should be a first-class citizen in Symfony, but Symfony should use the > standard Doctrine way of doing things. > > Fabien > >> On Thu, 09 Dec 2010 17:12:38 +0100, Fabien Potencier >> <[email protected]> wrote: >>>> >>>> No, Doctrine already supports all this. The DoctrineBundle is what >> makes >>>> it so unflexible. >>>> >>> >>> So if I understand correctly, you want to: >>> >>> * remove the "automatic" code added by the Doctrine bundle >>> * add support for the new syntax, which is just a way to configure the >>> "standard" Doctrine mapping objects. >>> >>> Correct? >>> >>> Fabien >> -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
