Re: Not sure where to report this bug

----- Original Message ----- From: "Martin Jansen" <mail@martin-jansen.de> To: "Brian Abent" <brian@onlineinfo.net> Cc: <pear-dev@lists.php.net> Sent: Friday, March 15, 2002 8:02 AM Subject: Re: [PEAR-DEV] Not sure where to report this bug > On Thu, 14 Mar 2002 14:10:15 -0500, Brian Abent wrote: > > >db_error Object > >( > > [error_message_prefix] => > > [mode] => 1 > > [level] => 1024 > > [code] => -19 > > [message] => DB Error: no such field > > [userinfo] => select > >username,user_id,password,name_first,name_last,users.active from users > >where ((upper(username) like upper('%brian%')) or (upper(name_last) like > >upper('%brian%'))) [nativecode=ERROR: Attribute 'name_first' not > >found > >] > > That's no bug in PEAR DB: The code you are using sends a bogus > SQL query to the server. Please see the content of "userinfo" > for the full error message ;-). > > - Martin > PEAR DB returns the proper error. The problem occurs when I try to check the return of db->query with PEAR::isError(). A warning comes up saying 'problem with method call. please report this bug.' isError() is not returning TRUE when given a valid error object from PEAR DB. Is isError() deprecated? The reason I posted the dump of $dbr was to try and show that isError() was being passed a real,valid error object and was not performing properly. -brian