mysql_result() VS mysql_fetch_row

[sempuritoza]

greetings

i had a look in the php manual and it said that once you start using bigger data sets its advisable to use function that return entire rows i.e. mysql_fetch_row but i just have a couple of questions.

1. can i assume then that when working with smaller data sets its better to use mysql_result?
2. what is the size - how many records - where one should start considering using the mysql_fetch_row() functions instead of the mysql_result function?

thanx
E

[laserlight]

A general rule of thumb would be:
Use mysql_result() when SELECTing a single column.
Use mysql_fetch_array(), mysql_fetch_assoc() or mysql_fetch_row() when SELECTing multiple columns.

But actually, since the mysql_fetch_*() functions can work with just a single row, one may simply forgo the use of mysql_result().

what is the size - how many records - where one should start considering using the mysql_fetch_row() functions instead of the mysql_result function?

Profile your code to find out, but I generally wouldnt bother with mysql_result().

[sempuritoza]

what are you, some kind of php guardian angel??? 😃

thank you

[Weedpacket]

About the only time I use mysql_result is when my query is only going to be returning one row with one field (typically a "SELECT COUNT(*)...". Just seems a bit silly to have the extra array step in that situation.