I was wondering, when you have a large set of data in a MySQL table, is it faster to find the data you want with MySQL's Select function, or by dumping the whole table into a PHP array and searching through that?
Basically, which works faster with lots of data, PHP or MySQL?
>>4-5 are both failing to use the two important words that PHP programmers in general seem to be oblivious to: query optimization. If you write your queries properly, the database can cut down something that you might implement in three ugly nested loops manipulating two nested sets of associative arrays, as one btree lookup and a string comparison. Simply put, the database knows much more about the data than the view does.
However, in order to properly make use of this fact, you still need to construct your databases non-stupidly. That's where all those principles of normalizing data and setting up indexes and so on really make a difference between a big box that you throw all your paperwork into haphazardly and then sort them one at a time when trying to find what you want, versus a well-organized filing cabinet with labeled hanging folders in alphabetical order.
>>6
Listen to this man.
And brush up your SQL.
and you're all forgetting to remind OP that premature optimization is the root of all evil. are you sure it's the table lookup that's taking most of your time?
everyone knows the only way to optimize is assembly, you must write your cgis in assembly php is toy language enjoy your sql injection