php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #13082 PEAR produces warnings with error_reporting = E_ALL
Submitted: 2001-08-31 13:38 UTC Modified: 2001-10-06 13:58 UTC
From: fidian at commnav dot com Assigned:
Status: Closed Package: *Database Functions
PHP Version: 4.0.6 OS: Linux
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: fidian at commnav dot com
New email:
PHP Version: OS:

 

 [2001-08-31 13:38 UTC] fidian at commnav dot com 
Set error_reporting to E_ALL and use the PEAR database functions.

Warning: Undefined property: prepare_maxstmt in /usr/local/lib/php/DB/common.php on line 287

That line is

$stmt = (int)$this->prepare_maxstmt++;

It looks like the constructor should just set prepare_maxstmt to zero to avoid the warning.  Another:

Warning: Undefined offset: 1103 in /usr/local/lib/php/DB/common.php on line 126

In looking at the code, I bet a lot of statements could use "if isset($var)" type of conditions before accessing them.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-10-06 13:58 UTC] mj@php.net 
This has been fixed in CVS.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Dec 26 12:01:30 2024 UTC