#22033 [Opn->Bgs]: Kryptic errors when not using "portability" option in DB
| From: | lsmith@php.net | Date: | Sun, 27 Apr 2003 21:17:44 +0000 |
| Subject: | #22033 [Opn->Bgs]: Kryptic errors when not using "portability" option in DB | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-15621@lists.php.net to get a copy of this message | ||
ID: 22033
Updated by: lsmith@php.net
Reported By: stamer at uni-oldenburg dot de
-Status: Open
+Status: Bogus
Bug Type: PEAR related
Operating System: Linux & Oracle
PHP Version: 4.3.0
New Comment:
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
PEAR DB always returns error objects when errors occur.
Please see the manual for details, specifically:
http://pear.php.net/manual/en/core.db.iserror.php
Previous Comments:
------------------------------------------------------------------------
[2003-02-03 10:34:49] stamer at uni-oldenburg dot de
Hi,
This is not really a bug, but it may take to too much time to
track the source of error.
I am using Linux with Oracle9. If I use e.g. DB_Result::numRows()
without option set to "portability"
(didn't know about it, first...), I get really kryptic
error messages, since an object is returned instead of an
expected integer.
This yields then "Unsupported operand types" if you try to
subtract an integer, and one really does not know what is going on.
Greetings, Heinrich
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=22033&edit=1