October 15, 200916 yr Hey, I have a tool that produces around 30-100 results every time it's run. Currently I have it stored as individual rows (so 30-100 rows) and group the results by date. I need some advice... Would you, instead of having say 100 rows, have a single row and have the 100 results in a single column then handle the data with PHP (instead of mysql)? That would reduce the amount of rows made but I can see an issue with ordering the arrays (theres multiple arrays with different types of data). Or is it not an issue? Lots of rows is acceptable? Sorry if this doesn't make much sense. I'm just wondering what the "fors" and "againsts" are for having too many rows... Cheers
October 17, 200916 yr Personally I find that keeping logs of data as individual items. You can always create "smart" queries that will get your data as you want it in preparation for PHP processing. As you say you can group your data with a query. Its much easier looping through all your results, and collating your data with php code when SQL can do it for you
October 20, 200916 yr Personally I find that keeping logs of data as individual items. You can always create "smart" queries that will get your data as you want it in preparation for PHP processing. As you say you can group your data with a query. Its much easier looping through all your results, and collating your data with php code when SQL can do it for you As long as you're indexing the correct columns, the number of rows shouldn't really matter.
Create an account or sign in to comment