Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:4939
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: PHP Internals <internals@lists.php.net>
Date: Thu, 23 Oct 2003 14:58:43 +0200
User-Agent: KMail/1.5.1
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-ID: <200310231458.43857.cesare@ngi.it>
Subject: Re: [PHP-DEV] database driver: no more rows
From: cesare@ngi.it (Cesare D'Amico)

Alle 00:18, gioved=EC 23 ottobre 2003, Lukas Smith ha scritto:
> run query that works
> run query that doesn't
>
> now when you fetch the rows of the first query you will usually
> determine if you hit the end if the result set by checking if you
> don't get an array returned
>
> if you don't get an array you check for an error and in several ext
> you will get the error created by the second query. This is also
> caused by the fact that the error checking simply returns the last
> error which cant be cleared appearently.

But can't you resolve this problem by checking if the query worked just=20
after issuing it? I mean, do something like:

=2E run query 1
=2E check if q1 worked
=2E run query 2
=2E check if q2 worked
=2E if q1 worked -> fetch data

=2E..and so on.

Perhaps I'm missing something, but I can't see a real issue here.

=2D-=20
Cesare D'Amico - http://www.phpday.it
"E` un'emergenza!!! Dovrei fare questo-e-questaltro ma non=20
posso perche' la mia testa e` piena di segatura e criceti!!!"
     -- un utente [ http://www.soft-land.org/storie/ ]