Or you can use Bindable Behavior to manage your bindings and recursives...
http://bakery.cakephp.org/articles/view/bindable-behavior-control-your-model-bindings Cheers, mbavio On Apr 30, 10:08 pm, validkeys <[EMAIL PROTECTED]> wrote: > you're the best dave, thanks! > > On Apr 30, 6:36 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > Well, it's always good practice to try not to pull related data from > > the database if you don't need it, so setting recursive to 0 or > > temporarily unbinding relationship that you won't be using is a good > > idea. I personally have never had any problems with memory bottoming > > out because of pulling recursive data and while 18K is a lot of data, > > it seems like Cake and, more importantly, the server should be able to > > handle it. I guess it really depends on how many relationship you have > > and how deep they go. I have noticed that the bugger dramatically > > slows down response times though, so I'd give it a shot. > > Dave > > > On Apr 30, 4:03 pm, validkeys <[EMAIL PROTECTED]> wrote: > > > > thanks david, that could definetly be it. I always have the debugger > > > at 1. What about recursive = 2? That seems to be an insane amount of > > > data. I had a database with like 18000+ orders (I was just learning > > > cake at the time) and put the recursive to 2 and it obviously bottomed > > > out on memory. Do you think that it might not have had i had the > > > debugger at 0? > > > > On Apr 30, 5:58 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > > wrote: > > > > > The only time I've had memory problems with Cake is when I was using > > > > an undefined variable in my view. There was a bug in cakes debugger > > > > code (heh, ironic) that caused an infinte loop when this condition > > > > arose. It may be fixed now, but I'd check my views for switches based > > > > on variables that may not be set, etc. Also, the debugger in general > > > > seems to slow cake down A LOT in my experience. Try setting debug to 0 > > > > in your /app/config/core.php file and see if that helps. Otherwise, > > > > I'm not sure why the find function would cause you memory problems. > > > > > Dave > > > > > On Apr 30, 3:01 pm, validkeys <[EMAIL PROTECTED]> wrote: > > > > > > Hey Guys, > > > > > > I have been having some memory problems with using the built in find > > > > > functions with cake. I have been setting the recursive's low and > > > > > limiting the fields that are returned in the query. I was wondering > > > > > what I could be doing wrong? I started using a lot of $this->query()'s > > > > > in my model and creating my own model functions that way and so far it > > > > > has been working much better. > > > > > > What could I be doing wrong with the built in functions? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
