php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #50701 If MySQLi fails it must return a fatal error
Submitted: 2010-01-08 22:40 UTC Modified: 2010-01-09 03:21 UTC
From: gmblar+php at gmail dot com Assigned:
Status: Not a bug Package: MySQLi related
PHP Version: 5.3.1 OS: *
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: gmblar+php at gmail dot com
New email:
PHP Version: OS:

 

 [2010-01-08 22:40 UTC] gmblar+php at gmail dot com
Description:
------------
If MySQLi fails it must return a fatal error. A Warning is not enough.

Reproduce code:
---------------
<?php

$database = new MySQLi('127.0.0.1', 'invalid', 'invalid');

?>


Expected result:
----------------
Fatal error: mysqli::mysqli(): (28000/1045): Access denied for user 
'invalid'@'localhost' (using password: YES) in /- on line 3

Actual result:
--------------
Warning: mysqli::mysqli(): (28000/1045): Access denied for user 
'invalid'@'localhost' (using password: YES) in /- on line 3

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-01-09 03:21 UTC] johannes@php.net
A fatal error can not be handled in any way, so the user would get an empty page (as every serious production system has display_errors off, else it shows confidential info)

Instead you have to check for error which gives you the possibility to create a nice error page shown to your users.
 [2010-01-09 03:21 UTC] johannes@php.net
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php


 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Dec 21 13:01:31 2024 UTC