|
Posted by Michael Fesser on 07/31/07 08:36
..oO(GA)
>It seems the script stopped at a point where I made a call from a
>mysql table like this:
>
>$foo = mysql_fetch_array(mysql_query(SELECT * FROM table a WHERE id =
>12));
>
>Which always worked before. The difference now, though, is that table
>a is now empty. And the script stopped because of that. Without
>showing an error - even on the mysql side of things.
Do you use '@' anywhere to supress error messages? How does your
mysql_query() call look? Do you check for errors with mysql_error()?
>Is there some special circumstance as to why a script would stop
>because an empty set was returned?
It should not, unless it triggers a bug and crashes the webserver.
Very unlikely in this case.
Micha
Navigation:
[Reply to this message]
|