Re: Big problem with DB::isError!
| From: | Alan Knowles | Date: | Mon, 18 Aug 2003 12:18:51 +0000 |
| Subject: | Re: Big problem with DB::isError! | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-19978@lists.php.net to get a copy of this message | ||
it's not really urgently critical (getAll doesnt work with update/alter stuff. basically)
I'm sure just tell the user to use $db->query() when they do modifications... rather than getAll()
This can wait IMHO untill cox gets back to it..
Regards
Alan
nicos@php.net wrote:
Hello,-- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.comIt looks in every part of the code we use, if(DB::isError($res). But infact isError returns FALSE in case of error so we should use !DB::isError or just change the behaviour of isError ? Very easy to verify it with the bug #25003... Very urgent, need feedback ! #25003.