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

go to bug id or search bugs for

Request #12512 E_INFO/E_USER_INFO
Submitted: 2001-08-01 08:27 UTC Modified: 2010-12-17 12:28 UTC
Votes:2
Avg. Score:1.0 ± 0.0
Reproduced:1 of 2 (50.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: yohgaki at hotmail dot com Assigned:
Status: Wont fix Package: *General Issues
PHP Version: 4.0.6 OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
35 + 47 = ?
Subscribe to this entry?

 
 [2001-08-01 08:27 UTC] yohgaki at hotmail dot com 
I would like to treat all E_NOTICE/E_USER_NOTICE as fatal error for my applications. However, newer pgsql extension raise E_NOTICE when transaction cannot be finished. (There is notice errors for resetting cache also) I like it, but I need to parse E_NOTICE message to check if it is fatal or not.

How about to have a E_INFO/E_USER_INFO for infomational errors?

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-12-17 12:28 UTC] jani@php.net
-Status: Open +Status: Wont fix -Package: Feature/Change Request +Package: *General Issues
 [2010-12-17 12:28 UTC] jani@php.net 
How about not.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Apr 20 03:01:28 2024 UTC