What are you intending to do with $peek? You only use it once and it's
sucking up one of your rows.
-jm
-Original Message-
From: Warren [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 21, 2001 5:33 PM
To: [EMAIL PROTECTED]
Subject: seemingly anomalous behaviour in Selects en
I think your command
$peek = @mysql_fetch_row($ex);
fetches the first row - you don't output it - and the cursor goes
to the next row.
For all remaining rows you use mysql_fetch_array($ex) which
starts from the second row (see above). This results in n rows,
with the first one invisible and
PROTECTED]
Subject: seemingly anomalous behaviour in Selects entered manually
vs.
in a script
Hi!
I've got this seemingly anomalous situation that occurs when using a
SELECT.
If I use the MYSQL command line thing and SELECT * FROM QUESTIONS, it
tells
me that there are 7 rows in the set. Ther
Hi!
I've got this seemingly anomalous situation that occurs when using a SELECT.
If I use the MYSQL command line thing and SELECT * FROM QUESTIONS, it tells
me that there are 7 rows in the set. There are, in fact 7 rows. Perfect.
HOWEVER, if I execute the following script I always get 1 row
