Re: Big problem with DB::isError!
| From: | nicos@php.net | Date: | Mon, 18 Aug 2003 12:21:39 +0000 |
| Subject: | Re: Big problem with DB::isError! | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-19980@lists.php.net to get a copy of this message | ||
----- Original Message -----
From: "Alan Knowles" <alan@akbkhome.com>
To: <nicos@php.net>
Cc: <pear-dev@lists.php.net>
Sent: Monday, August 18, 2003 2:18 PM
Subject: Re: [PEAR-DEV] Big problem with DB::isError!
> 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..
>
Well yes, in fact we need an error handling before try to fetch any queries
that are not fetchable..
> Regards
> Alan
>
>
>
>
>
> nicos@php.net wrote:
> > Hello,
> >
> > It looks in every part of the code we use, if(DB::isError($res). But
in
> > fact 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.
> >
>
>
> --
> Can you help out?
> Need Consulting Services or Know of a Job?
> http://www.akbkhome.com