php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #9510 OCIError function with no params does *NOT* return the "last" error
Submitted: 2001-03-01 11:48 UTC Modified: 2001-05-04 10:41 UTC
From: merrill at missioncriticallinux dot com Assigned:
Status: Closed Package: OCI8 related
PHP Version: 4.0.4pl1 OS: Redhat 6.1 Linux
Private report: No CVE-ID: None
 [2001-03-01 11:48 UTC] merrill at missioncriticallinux dot com
PHP 4.0.4pl1

'./configure' '--prefix=/var/php' '--with-config-file-path=/var/php' '--enable-track-vars'  '--enable-sigchild' '--with-apache=../apache_1.3.14' '--with-ftp'
                                           '--with-mcrypt=/var/libmcrypt' '--with-pgsql=/var/postgresql'                                           '--with-oci8=/u01/app/oracle/product/8.1.6' '--with-mysql=/var/mysql'

According to the OCIError documentation, OCIError invoked with no parameters is supposed to return the *last* error.  But here's an example where OCIError invoked with no parameters returns *no* error.  This should be fixed to return the last error.

Given this SELECT

   select abc from customer


with a column that does NOT exist("abc") in table "customer", the OCIExecute returns "false", but then OCIError() invoked with no parameters is supposed to return the "last" error, but returns no error.  In this case, OCIError($cursor) invoked with the $cursor parameter *does* return the proper error:

  ORA-00904: invalid column name


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-05-04 10:41 UTC] thies@php.net
the documentation needs to be updated - ocierror always stores the error in the most appropiate (parent-)handle. 
 
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Wed Feb 08 18:03:46 2023 UTC