It'd be an interesting test, but from the outset I (unscientifically) doubt it. Without the contain behaviour and relying on recursive = whatever you are often pulling back way too much data, so some sort of model binding adjustment has to save horsepower. The containable behaviour simply manages the process of binding and unbinding, so I can't see how or why it'd be more inefficient than doing it yourself. I use it de facto and have not experienced any memory issues. Open to persuasion once I see some evidence though.
Jeremy Burns Class Outfit http://www.classoutfit.com On 12 Nov 2011, at 13:30, zuha wrote: > I saw this comment on another thread, and instead of taking over that thread > with a containable discussion, I'm starting a new one. Can anyone confirm or > deny this claim that "containable" uses a lot of memory? (as say compared to > bind/unbind) > > On Sat, Nov 12, 2011 at 5:47 PM, phpMagpie <[email protected]> wrote: > I would advise you to learn how to use containable ... only takes a > couple of lines of code makes life a whole lot easier than having to > bind and unbind for every paginate. > > > I'd like to avoid it. I think it consumes a lot of memory. CMIIW. > Thank you. > > -- > Our newest site for the community: CakePHP Video Tutorials > http://tv.cakephp.org > Check out the new CakePHP Questions site http://ask.cakephp.org and help > others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > [email protected] For more options, visit this group at > http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
