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.
If this is a once only import (populate initial db), I'd stick to
using mysql's data import command line tool and move onto something
more fun.
If it's something that needs to be run repeatedly e.g. a user uploads
a file that needs to be imported then write a custom method in the
Model that uses
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
Thanks for the response - the idea of 'minimizing data that PHP
processes' as a design pattern for PHP web apps is an insight that I
had totally missed, and appreciate your pointing it out. It also
helps to explain why there isn't a whole lot on the internet about
perf tuning/profiling CakePHP
Well, again, it's not a matter of can or can't, the thing is, there's
no why... even wanting a full featured view, with whole lots of data
of all sorts of associations and purposes, what you have to keep in
mind is, why? : where does it fits in your app design? and if you
ever planned it or just
Thanks for the advice!
The 'Just Build It' thing is good, and pretty much how I arrived at
the point that Im currently at. Since I'm doing this as a side-thing
(I mostly teach, and I'm doing this app on my own time), I'm worried
about being slammed by my app not scaling well, and me having to
Hello!
I'm trying to load a bunch of rows into a table - on the order of
1,000 or so. This isn't huge, but I'm having problems when I try to
do it using CakePHP. My basic approach is to upload a .CSV file,
which i then pull apart, and use to repeatedly save() new rows into
the appropriate
Hey Mike, it's totally not a matter of performance here.
First of all, there's no reason on use this approach for a that huge
amout of data, you should probably import it to your db.
But if you want to do this in the app layer, maybe it's a feature - I
don't know, you should definetly build
