RE: seemingly anomalous behaviour in Selects entered manually vs. in a script

2001-02-21 Thread Javier Muniz
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 entered m

Re: seemingly anomalous behaviour in Selects entered manually vs. in a script

2001-02-21 Thread Guenther Pewny
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

RE: seemingly anomalous behaviour in Selects entered manually vs. in a script

2001-02-21 Thread Johnny Withers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 $peek=@mysql_fetch_row($ex); while($row = mysql_fetch_array($ex)) at that point in your code the first call to mysql_fetch_row() moves the result pointer up one position.. therefore, losing your first row. if you have to have $peek.. make a call t