php 5 and mysql failure

On 5 Mag, 19:05, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> Caffeneide wrote:
> > On May 5, 2:13 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> >> Caffeneide wrote:
> >>> On Apr 30, 5:38 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> >>>> Caffeneide wrote:
> >>>>> I'm using a php script which performs three xml queries to other three
> >>>>> servers to retrieve a set of ids and after I do a query to mysql of
> >>>>> the kind
> >>>>> SELECT * FROM table WHERE id IN ('set of ids');
> >>>>> Although I'm sure the connection to the database is ok, I sometimes
> >>>>> get an error of this kind:
> >>>>> *Warning*: mysql_fetch_object(): supplied argument is not a valid
> >>>>> MySQL result resource in ...
> >>>>> This does not happen every time i run the script, only sometimes.
> >>>>> If I echo the query, copy and paste in phpmyadmin, or if I perform the
> >>>>> same query in a script that does only the query without the rest it
> >>>>> works!
> >>>>> After troubleshooting this issue I noticed that it usually failed when
> >>>>> I had a big set of ids (positive response from more than one server).
> >>>>> This means that the script used a bigger amount of memory and probably
> >>>>> more resources, but I did not get an "out of memory error", I got the
> >>>>> one described before.
> >>>>> My question is, is there any kind of limit somewhere in php5 or in
> >>>>> mysql (version 5)?
> >>>>> Thanks for help,
> >>>>> YEHUDI GARRETT
> >>>> It's possible you're running into a limit, but it's quite large.
> >>>> The "supplied argument is not a valid MySQL result resource" indicates
> >>>> your mysql_query() returned false, probably. You should ALWAYS check
> >>>> the result of mysql_query(), and if it fails, log the error (you really
> >>>> don't want to display those errors to your users, do you?). Or, on a
> >>>> development system, display the error.
> >>>> --
> >>>> ==================
> >>>> Remove the "x" from my email address
> >>>> Jerry Stuckle
> >>>> JDS Computer Training Corp.
> >>>> jstuck...@attglobal.net
> >>>> ==================
> >>> Probably it's a problem related to php and mysql. if I copy and paste
> >>> the query in phpmyadmin it always works, so I wouldn't say it's a
> >>> mysql limit problem.
> >> Probably it's a problem in your code. If it were a problem related to
> >> php and mysql, phpmyadmin would fail also - it is also php and mysql.
>
> >> --
> >> ==================
> >> Remove the "x" from my email address
> >> Jerry Stuckle
> >> JDS Computer Training Corp.
> >> jstuck...@attglobal.net
> >> ==================
>
> > Thank you Jerry, useful hint. This is the error logged: 2006: MySQL
> > server has gone away
>
> > Where has he gone? What can be the problem?
>
> OK, now we're making some progress. This is a MySQL failure, not one in
> PHP (although your query may still have problems).
>
> You need to follow this up on comp.databases.mysql (where I see you also
> started a thread).
>
> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> JDS Computer Training Corp.
> jstuck...@attglobal.net
> ==================

thanks, it's seems I resolved this error increasing the value of MySQL
"wait_timeout" options...thank you!