Absolutely baffled why mysql_fetch_row() is not working

rtcary

I have used mysql_fetch_row in other places in the application where it works as expected, but in one function it is NOT returning the value in field[0]. This is a snippet of the code with my test lines:

    $stmnt = "SELECT COUNT(*) FROM Sessions " .
             "WHERE SessionID = " . $this->fieldnullquote($session_id);
    $result = mysql_query($stmnt, $this->link);
    $row = mysql_fetch_row($result);
print_r($stmnt . "<br>");
print_r($result . "<br>");
print_r($row . "<br>");
print_r(mysql_field_name($result, 0) . "<br>");
print_r(mysql_num_fields($result) . "<br>");
print_r(mysql_num_rows($result) . "<br>");
print_r($row[0] . "<br>");exit;

And here are the results:

SELECT COUNT(*) FROM Sessions WHERE SessionID = '41922549952d2ffe8916d08.43055088'
Resource id #9
Array
COUNT(*)
1
1

$row[0] should return a value of 1 as the query does in phpMyAdmin and as is shown by the results of

print_r(mysql_num_rows($result) . "<br>");

I know mysql_fetch_row will be deprecated, however it is working else where in the application.

Probably the error is too obvious for me to see...been looking at this for a LONG time.

Baffled,

Todd

NogDog

mysql_num_rows() will always return 1 for that query, since it will always return one row. However, the value of the only column in that row may be 0 if no match is found in that table for filtering specified in the where clause. So for now I have to assume there was no exact match for "41922549952d2ffe8916d08.43055088" in that column in that table in that database. (Are you sure the column is the correct type and length to hold that value, and that is is not being padded in some way?)

rtcary

I double check the query by running the $stmnt in phpMyAdmin [see image]:

[ATTACH]4983[/ATTACH]

The test data on which the query is based is

SELECT COUNT() FROM Sessions WHERE SessionID = '211002388752d4105434d842.79482680'
Resource id #9
Array
COUNT()
1
1

Not sure what to try to get an idea of what is going on?!?

Todd

Query.jpg

NogDog

Just to eliminate the ridiculous, are you sure your script is connecting to the same database server and database as your phpMyAdmin is?

Assuming that's not the issue, just for the fun(?) of it, how about changing the query to:

SELECT COUNT(*) [COLOR="#FF0000"][B]AS fubar[/B][/COLOR] FROM Sessions ...

Then instead of using mysql_fetch_row(), use mysql_fetch_assoc(), and see what is then in $row['fubar']. (No, I don't really think that should make a difference, but then at least we'd know if $row actually has a 'fubar' element or not.

(Probably the real problem is something so simple neither of us is seeing it.)

bradgrafelman

You might also want to do a print_r() (or, even better, [man]var_dump/man) on $row itself (something you haven't done yet).

rtcary

Thank all for your patience!! Yes, it was nothing to do with the actual code; it had to do with the loose nut between the keyboard and the chair! The script that was giving me the headache and was calling the exact same classes had an include line at the top (variable initialization) that does not exist. Why that did not throw an error beats me!

The hours I wasted! And yours too!

Sorry...

Todd

Derokorian

You can check if include was successful, but if you need the file to be included always, it is better to use require, because php will die when it can't require something, unlike includes.

johanafm

rtcary;11037129 wrote:
Why that did not throw an error beats me!

Check the docs and your php.ini to find out default settings for what gets reported as errors.

The value for error_reporting may also be changed at runtime. It can be both inspected and changed using [man]error_reporting/man. Setting it to -1 will enable all errors.

Furthermore, you will also need to properly set log_errors and/or display_errors.

This is simply so that you know about how to setup error reporting. If you need the file to be included at all times, follow Derokorian's advice.