I can see that changing the behavior of arrayDeepMerge is scary, but the Symfony book proudly promotes extending schemas in this way for both Doctrine and Propel... the fix needs to work for both of them. Perhaps that means implementing a fix in both plugins.
On Mon, Jan 11, 2010 at 1:47 PM, nervo <[email protected]> wrote: > Nice :) > > I saw few issues about sfToolkit::arrayDeepMerge() and associative > arrays in symfony trac. The answer is always the same : too risky to > fix ! > > From my point of view, sfToolkit::arrayDeepMerge() should be rewritten > only for sf 2, and sfDoctrinePlugin should use another method to merge > doctrine schemas. > > On Jan 11, 7:35 pm, Kris Wallsmith <kris.wallsm...@symfony- > project.com> wrote: >> I was talking with jwage about this a few days ago and I've come to think >> this is an issue that should be resolved in sfDoctrinePlugin. I'm not sure >> what that resolution is right now, but will try to get this fixed for the >> next release. >> >> Thanks, >> Kris >> >> -- >> >> Kris Wallsmith | Release Manager >> [email protected] >> Portland, Oregon USA >> >> http://twitter.com/kriswallsmith >> >> On Jan 11, 2010, at 9:52 AM, nervo wrote: >> >> > True. >> >> > In my case, it radically restrains the plugins decoupling of my >> > projects. >> >> > Any core developpers opinions, over there ? >> >> > On Jan 11, 5:19 pm, Tom Boutell <[email protected]> wrote: >> >> That would certainly be a Big Problem for anyone hoping to extend, >> >> say, the sfGuardUser table in a project in which other plugins do so >> >> as well. >> >> >> On Sat, Jan 9, 2010 at 7:10 AM, nervo <[email protected]> wrote: >> >>> I'm sorry to use this mailing list, but i'm little worried about the >> >>> issue #7701 (http://trac.symfony-project.org/ticket/7701). >> >> >>> At this time, it's not possible to extend docrine stuff (schema, >> >>> listeners, behaviors, ...) in more than ONE plugin, because of a >> >>> limitation of sfToolkit::arrayDeepMerge() wich do not support true >> >>> associative arrays merging. >> >> >>> This issue has not been reviewed nor planned for next symfony >> >>> releases, maybe i'm the only one who see the benefits of such >> >>> feature :) >> >> >>> -- >> >>> 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 >> >>> athttp://groups.google.com/group/symfony-devs?hl=en. >> >> >> -- >> >> Tom Boutell >> >> P'unk Avenue >> >> 215 755 1330 >> >> punkave.com >> >> window.punkave.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 >> > athttp://groups.google.com/group/symfony-devs?hl=en. > > -- > 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. > > > > -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.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.
