consecutive mysql UPDATE queries

hailey

If I put an UPDATE query right after another, like this:

mysql_query("UPDATE table SET a=1");
mysql_query("UPDATE table2 SET a=1");

It seems to skip the first one! I assume it's because PHP doesn't wait for mysql to actually execute the command. PHP sends the first query, and then sends the next one right away, before mysql can actually do anything with the first one.
Is that correct?

I haven't tried this with INSERT queries, but I assume the same thing would happen.

At any rate, how exactly do you get around this problem?

swr

Huh?

If you do what you specified, I'm pretty sure it will set a=1 for all rows in table and table2.

Are you sure the first one is succeeding? Whenever you call [man]mysql_query[/man] you should call it like this:

mysql_query("your_query_here") or die(mysql_error());

If you leave out the "or die..." part, then any problem will cause the query to fail without any notice of any kind, leaving you scratching your head wondering what happened. ALWAYS use the "or die(mysql_error())" when calling mysql_query, then if there's a problem you'll know what it was.

hailey

Well that's really weird...

I know that the queries are indeed working. They work on their own, but when I put one after the other like I showed before, it doesn't seem to work properly. However, if I add sleep(), like this:

mysql_query("UPDATE table SET a=1");
sleep(1);
mysql_query("UPDATE table2 SET a=1");

It works! The only problem is, they build up over time, and it gets really annoying to have to wait for things to happen. If I had 6 updates going, for example, I would have to put 5 sleeps in between them for it to work. That's 5 seconds of waiting, for something that should only take milliseconds or less. I tried using usleep(), but if it's too short of a time, it does the same thing as if it weren't there! (No, I'm not running Windows, so usleep() does indeed work.)

So... I don't know what the heck is wrong then.

hailey

Anyone have any idea what might be wrong??

Are there any server settings or anything that might produce this problem?