Ugh! But bear in mind that cakePHP (and all MVCs -- or at least all the ones using 'Active Record') attempt to keep as much database logic in the background and still in PHP as possible. That's *not* a large capacity environment, when compared to MySQL itself. Do you have any interest in investigating a MySQL stored procedure as an alternative? I have exactly 0 experience with this sort of thing in MySQL, but I have found occasion in MSSQL to do this -- usually to get memory-intensive work *out* of my page and into the DB server. I'd imagine a custom model built to access such a construct would be fairly trim...
MM On Mon, Jul 4, 2011 at 9:21 AM, DanielMedia <danielmedi...@gmail.com> wrote: > I definitely would have been ok with just using the query() method. > The problem is that the save() method also accumulates memory in each > iteration. I ran the script for a while with the save() method > commented out and the memory remained low and constant. Once I try to > save, the memory jumps up again on each iteration. I was hoping I > wouldn't have to write a huge SQL statement for the save as well. > Kinda goes against the whole point of using CakePHP to begin with : ( > > -- > 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 > cake-php+unsubscr...@googlegroups.com 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 cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
