Re: database driver: no more rows

From: Date: Thu, 23 Oct 2003 12:58:43 +0000
Subject: Re: database driver: no more rows
Groups: php.internals 
Request: Send a blank email to internals+get-4939@lists.php.net to get a copy of this message
Alle 00:18, giovedì 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 after issuing it? I mean, do something like: . run query 1 . check if q1 worked . run query 2 . check if q2 worked . if q1 worked -> fetch data ..and so on. Perhaps I'm missing something, but I can't see a real issue here. -- Cesare D'Amico - http://www.phpday.it "E` un'emergenza!!! Dovrei fare questo-e-questaltro ma non posso perche' la mia testa e` piena di segatura e criceti!!!" -- un utente [ http://www.soft-land.org/storie/ ]

« previous php.internals (#4939) next »