|
|
Posted by Rik on 08/02/07 03:45
On Thu, 02 Aug 2007 05:35:25 +0200, GA <fang27@excite.com> wrote:
> On Tue, 31 Jul 2007 00:30:07 +0200, Rik <luiheidsgoeroe@hotmail.com>
> wrote:
>
>> On Mon, 30 Jul 2007 23:19:41 +0200, GA <fang27@excite.com> wrote:
>>> It seems the script stopped at a point where I made a call from a
>>> mysql table like this:
>>>
>>> $foo =3D mysql_fetch_array(mysql_query(SELECT * FROM table a WHERE i=
d =3D
>>> 12));
>>>
>>> Which always worked before. The difference now, though, is that tab=
le
>>> a is now empty. And the script stopped because of that. Without
>>> showing an error - even on the mysql side of things.
>>
>> So, immidiately after it stopped, no further evaluation? I would expe=
ct
>> $foo just to be false... It does here:
>>
>> $foo =3D mysql_fetch_array(mysql_query('SELECT * FROM bar a WHERE id =
=3D =
>> 12'));
>> var_dump($foo);
>>
>> result:
>> bool(false)
>>
>> Are you sure this is where it stops? Not an argument further? I assum=
e =
>> the
>> query was correct (table exists etc) else you'd get a warning the =
>> argument
>> was not a valid resource.
>
> Yes, it does stop. I commented out the whole script below it, made
> sure it was making it to that statement, and used mysql_error() to ask=
> for anything weird.
>
> Nothing happens - script just stops based on a return from an empty
> table. This is very weird - I have other scripts that make similar
> calls for other sites, and they don't just stop suddenly.
Either display_errors is set to false, or error_reporting is set to =
something it shouldn't. Enable both (or possibly log errors and examine =
=
the file), and check again.
-- =
Rik Wasmus
Navigation:
[Reply to this message]
|