Mike, I think it's not "how much data is Cake intended to deal with" is how much data your app is intended to deal with, thousands of records is not something that should be dealed by php, the database does it much faster and safer. Having lots of data in database doesn't mean you have to deal with them always - I would say ever - because you would rarely want users stumbling their heads on to a 800+ rows report, I would say that using a 30+ limit in a report/index is already annoying. Now how do you intend to support thousands of records include in the app database if not with a file upload? there's no way to make a user fill more than three forms at once... And as the database can handle files, al you have to do is parse the file if needed.
Cake loves you and will do lots of things for you, but it's still php and still uses memory, relies on cpu process and all this stuff. rafaelbandeira3 http://rafaelbandeira3.wordpress.com On 24 set, 03:25, Mike <[EMAIL PROTECTED]> wrote: > Thanks for the tip! In the previous, non-Cake version of the app, I > did that exactly, so it shouldn't be too too tough to get it up and > running again. I was kinda avoiding SQL b/c it seemed like "the Cake > way" should be to push it through the Cake layer & let CakePHP make it > automagically happen. Hearing that raw SQL is actually the right way > is actually really helpful :) > > If you don't mind my asking a couple more questions - how does one > know where the boundary should be? I mean, aside from exceeding > max_execution time and/or running out of memory - how would I know > where to draw the boundary between 'small enough for Cake' vs. 'needs > raw SQL' when designing my app? (And what does a normal app do if a > user happens to show up with an unexpectedly huge data set?) > > Also, what sort of data sets is Cake intended to support? I'm writing > the app to support my teaching, so having 30 people in a class, with > 10-20 homeworks/exercise sets to hand in (each of which might have 2-3 > versions stored), so it's conceivable that Cake might auto-magically > pull 600-1,200 records (even if fairly few / none of them are used in > any given view). One of the things I really liked about Cake was that > I could set recursive = 2 (or 3), and have it magically pull > everything I needed out of the DB (in my raw PHP app, I figured it was > time to look at a framework when I started to move towards an OOP-y > iterator approach for dealing with all my lists of data :) ) > > Thanks again for the quick reply - I appreciate the 'ok' from someone > who knows more about this than I do! :) > --Mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
