php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #14328 Interbase and error handling
Submitted: 2001-12-03 14:58 UTC Modified: 2002-04-13 14:49 UTC
From: sergio at corecanarias dot com Assigned:
Status: Closed Package: InterBase related
PHP Version: 4.0.6 OS: Linux Red Hat 7.1
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: sergio at corecanarias dot com
New email:
PHP Version: OS:

 

 [2001-12-03 14:58 UTC] sergio at corecanarias dot com
This may can't be exactly a bug, maybe you can consider it as a not implemented feature (I'm not sure about it).

Well, when I'm triying to handle error generated by any Interbase function, it doesn't work. When I try the same with a MySQL function all goes ok. I'm interested in show my own error messages but it's imposible to handle any error generated by Interbase function. I have tried with error_handling(0), with the @ operator before the function, putting error_handling to 0 and ~E_ALL in PHP.INI but Interbase function always returns it own error message.

For example I have this code in a object constructor:

$this->IBConnection = @ibase_connect($this->SQLEDatabase, $this->SQLEUser, $this->SQLEPass, 'NONE', '0', '3');
if (!$this->IBConnection)
   trigger_error("No se pudo conectar con la base de datos", E_USER_ERROR);

Then, it first shows me the default error message and then my own generated error message...

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-04-13 14:49 UTC] daniela@php.net
The version of PHP that this bug was reported in is too old. 
Please try the php-4.2.0RC3 from http://www.php.net/~derick/ 

If you are still able to reproduce the bug, please change the PHP
version on this bug report to the version you tested and change 
the status back to "Open".

 
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Mon Aug 15 15:05:45 2022 UTC