I've got a dataset that's just over 400k rows (and will shortly be 6 times that size) and I'm trying to come up with the most efficient query. Right now, I'm playing with finderQuery but the script consistently runs out of memory, though php.ini has been given 128MB.[1] While I'm fairly certain that I won't get as good performance using Cake-created queries as I would with one, custom one, I'm interested in seeing what the difference is.
So, I'm trying to figure out where I can throw in some debug() calls and an exit() in order to see what Cake is trying to do *before* it actually tries the DB query (and, thus, commits suicide). From what I understand, Cake will not issue just that one query designated as the finderQuery, but issues at least one other query before that. I'm trying to learn whether I've got that right (and, if so, what the query is). I'd really appreciate some pointers as I'm getting a bit lost wading through DboSource and I'm not even sure that this is the file I should be poking around in. [1] Because this site will not be on my own server, this amount of RAM is unlikely to be available in php.ini. I've bumped it up solely to try to get the script to finish so I can see how the query worked out. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
