Posted by Knut Krueger on 11/24/07 09:34

Jerry Stuckle schrieb:
> Knut Krueger wrote:
>> Michael Fesser schrieb:
>>> .oO(Knut Krueger)
>>>
>>>> withour talking abut the SQL problem - see the other guys it should
>>>> be possible to prvent the error message with
>>>>
>>>>
>>>> $data = @mysql_fetch_array($result,MYSQL_ASSOC))
>>>>
>>>> I do not know whether it is working with
>>>> mysql_fetch_array($result,MYSQL_ASSOC))
>>>> but it is working with @mysql_query and @mysql_num_rows
>>>
>>> Using '@' is really bad style in most cases. It suppresses the error
>>> message instead of fixing it.
>>>
>>> Micha
>> but it is better to supress one error instead of setting
>> error_reporting off, isn`t it?
>> Regards Knut
>>
>
> It's better to not cause the error in the first place.

Just one question to the sql problem.
where is technical the difference (count of SQL branches cpu cycles
etc.) to look for an entry suppress the error if, it is not there and
branch to the "error routine" instead using an other PHP-SQL call to
look for the record without error, and branch to the same "error
routine"? Both ways seems to be equal in the result.

Regards Knut

>

[Back to original message]